Quantcast

Reporting alpha4 bugs

classic Classic list List threaded Threaded
10 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Reporting alpha4 bugs

Doug
What's the most useful way for me to report possible bugs in
alpha4?
In Gramps-developers mailing list? On the bug tracker? Both
(or would that be like shouting)?

Doug

P.S. I recently reported a crash with Navweb (bug 6397).
It's been tagged by romjerome.
There's no target version; but I imagine it needs resolving
for 4.0.0.

------------------------------------------------------------------------------
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013
and get the hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb
_______________________________________________
Gramps-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Reporting alpha4 bugs

Tim Lyons
Administrator
Doug wrote
P.S. I recently reported a crash with Navweb (bug 6397).
It's been tagged by romjerome.
There's no target version; but I imagine it needs resolving
for 4.0.0.
I fixed this in rev 21292 before I even realised it was raised as a bug.

It is a fault in the recent changes to alive - Doug B, can you check that the change is the right one - it seems to be a simple problem.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Reporting alpha4 bugs

Tim Lyons
Administrator
Tim Lyons wrote
Doug wrote
P.S. I recently reported a crash with Navweb (bug 6397).
It's been tagged by romjerome.
There's no target version; but I imagine it needs resolving
for 4.0.0.
I fixed this in rev 21292 before I even realised it was raised as a bug.

It is a fault in the recent changes to alive - Doug B, can you check that the change is the right one - it seems to be a simple problem.
and gramps40 rev 21300
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Reporting alpha4 bugs

Doug
On 05/02/13 12:18, Tim Lyons wrote:

> Tim Lyons wrote
>>
>> Doug wrote
>>> P.S. I recently reported a crash with Navweb (bug 6397).
>>> It's been tagged by romjerome.
>>> There's no target version; but I imagine it needs resolving
>>> for 4.0.0.
>> I fixed this in rev 21292 before I even realised it was raised as a bug.
>>
>> It is a fault in the recent changes to alive - Doug B, can you check that
>> the change is the right one - it seems to be a simple problem.
>
> and gramps40 rev 21300
>

Thanks Tim.
Can you point me to the patch?

Doug


------------------------------------------------------------------------------
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013
and get the hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb
_______________________________________________
Gramps-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Reporting alpha4 bugs

John Ralls-2

On Feb 5, 2013, at 4:29 AM, doug <[hidden email]> wrote:

> On 05/02/13 12:18, Tim Lyons wrote:
>> Tim Lyons wrote
>>>
>>> Doug wrote
>>>> P.S. I recently reported a crash with Navweb (bug 6397).
>>>> It's been tagged by romjerome.
>>>> There's no target version; but I imagine it needs resolving
>>>> for 4.0.0.
>>> I fixed this in rev 21292 before I even realised it was raised as a bug.
>>>
>>> It is a fault in the recent changes to alive - Doug B, can you check that
>>> the change is the right one - it seems to be a simple problem.
>>
>> and gramps40 rev 21300
>>
>
> Thanks Tim.
> Can you point me to the patch?
>

He did. Just stick https://sourceforge.net/p/gramps/code/ in front of the rev number (so https://sourceforge.net/p/gramps/code/21300) and that's your patch.

However, since you're actively testing, you might find it easier to do a subversion checkout and work from that. Instructions at http://www.gramps-project.org/wiki/index.php?title=Brief_introduction_to_SVN

Regards,
John Ralls



------------------------------------------------------------------------------
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013
and get the hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb
_______________________________________________
Gramps-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Reporting alpha4 bugs

Doug
In reply to this post by Doug
On 05/02/13 14:06, Paul Franklin wrote:

> Note that this is only going to you, not the list.
>
> On 2/5/13, doug <[hidden email]> wrote:
>> On 05/02/13 12:18, Tim Lyons wrote:
>>> Tim Lyons wrote
>
>>>> It is a fault in the recent changes to alive - Doug B, can you check
>>>> that
>>>> the change is the right one - it seems to be a simple problem.
>
> I am guessing that the "Doug B" Tim had in mind was the
> developer Doug Blank -- but I'm only guessing.
>
>>> and gramps40 rev 21300
>>>
>>
>> Thanks Tim.
>> Can you point me to the patch?
>
> Tim will probably answer this one too, but I'm guessing
> that when he referred to "gramps40 rev21300"  as being the
> fix, that it is what you call the patch.  At least for gramps40.
>
> You can always go to the sourceforge web site (for gramps,
> sourceforge.net/p/gramps/code) and "go down" to the file you
> want then download it.  Or click on revision numbers to see what
> files changed, and the "diff" link to see the differences.
>
> To answer your original question, I'd say the bug tracker
> is the appropriate place.  Then if it (later) seems to be ignored
> you can mention it on gramps-devel ("I filed bug so-and-so
> on such-and-such and I wonder if anybody has looked at it?").
>
> Let me also mention that on the bug tracker, if you put an
> octothorpe/numbersign/poundsign character -- # -- ahead of
> some bug number, the bug tracker software will turn it into
> a link to that bug report.  That is, "6378" is just text but "#6378"
> (entered by you) will turn into a link to bug 6378.
>
> I also think the "target version" matters, so I'd suggest you fill
> in 4.0.0 automatically (for alphaN bugs that is).  I am guessing
> but I think that puts it on"the roadmap" for that release -- a list
> of pending bugs.  A developer can always change that number,
> if you have guessed wrong or they disagree.
>
> Thank you very much for being willing to help gramps test
> the new version.  The gramps community appreciates the help.

You're very welcome; and thanks, that's extremely helpful.

Doug

>


------------------------------------------------------------------------------
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013
and get the hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb
_______________________________________________
Gramps-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Reporting alpha4 bugs

Doug
In reply to this post by John Ralls-2
On 05/02/13 15:00, John Ralls wrote:

>
> On Feb 5, 2013, at 4:29 AM, doug <[hidden email]> wrote:
>
>> On 05/02/13 12:18, Tim Lyons wrote:
>>> Tim Lyons wrote
>>>>
>>>> Doug wrote
>>>>> P.S. I recently reported a crash with Navweb (bug 6397).
>>>>> It's been tagged by romjerome.
>>>>> There's no target version; but I imagine it needs resolving
>>>>> for 4.0.0.
>>>> I fixed this in rev 21292 before I even realised it was raised as a bug.
>>>>
>>>> It is a fault in the recent changes to alive - Doug B, can you check that
>>>> the change is the right one - it seems to be a simple problem.
>>>
>>> and gramps40 rev 21300
>>>
>>
>> Thanks Tim.
>> Can you point me to the patch?
>>
>
> He did. Just stick https://sourceforge.net/p/gramps/code/ in front of the rev number (so https://sourceforge.net/p/gramps/code/21300) and that's your patch.
>
> However, since you're actively testing, you might find it easier to do a subversion checkout and work from that. Instructions at http://www.gramps-project.org/wiki/index.php?title=Brief_introduction_to_SVN
>
> Regards,
> John Ralls
>

Thanks. After Tim's post the penny dropped!
As I'm trying out alpha4 installed from tarball maybe I
should stay with  patching for the moment, as it doesn't
give me any particular difficulty.


Doug

------------------------------------------------------------------------------
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013
and get the hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb
_______________________________________________
Gramps-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Reporting alpha4 bugs

Doug
In reply to this post by Doug
On 05/02/13 14:06, Paul Franklin wrote:
<snip>

>
> I also think the "target version" matters, so I'd suggest you fill
> in 4.0.0 automatically (for alphaN bugs that is).  I am guessing
> but I think that puts it on"the roadmap" for that release -- a list
> of pending bugs.  A developer can always change that number,
> if you have guessed wrong or they disagree.

I'm not sure how or whether I can do this.
I've just reported a couple more bugs (#6410, #6411) but
don't see any way to enter a "target version".

Doug


------------------------------------------------------------------------------
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013
and get the hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb
_______________________________________________
Gramps-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Reporting alpha4 bugs

Benny Malengier



2013/2/5 doug <[hidden email]>
On 05/02/13 14:06, Paul Franklin wrote:
<snip>

>
> I also think the "target version" matters, so I'd suggest you fill
> in 4.0.0 automatically (for alphaN bugs that is).  I am guessing
> but I think that puts it on"the roadmap" for that release -- a list
> of pending bugs.  A developer can always change that number,
> if you have guessed wrong or they disagree.

I'm not sure how or whether I can do this.
I've just reported a couple more bugs (#6410, #6411) but
don't see any way to enter a "target version".

Yes, it is up to people triaging the bugs to set target, as a submitter of a bug will normally always find it important.

Benny


------------------------------------------------------------------------------
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013
and get the hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb
_______________________________________________
Gramps-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Reporting alpha4 bugs

Doug
On 06/02/13 08:27, Benny Malengier wrote:

>
>
>
> 2013/2/5 doug <[hidden email] <mailto:[hidden email]>>
>
>     On 05/02/13 14:06, Paul Franklin wrote:
>     <snip>
>
>      >
>      > I also think the "target version" matters, so I'd
>     suggest you fill
>      > in 4.0.0 automatically (for alphaN bugs that is). Â I
>     am guessing
>      > but I think that puts it on"the roadmap" for that
>     release -- a list
>      > of pending bugs. Â A developer can always change that
>     number,
>      > if you have guessed wrong or they disagree.
>
>     I'm not sure how or whether I can do this.
>     I've just reported a couple more bugs (#6410, #6411) but
>     don't see any way to enter a "target version".
>
>
> Yes, it is up to people triaging the bugs to set target, as
> a submitter of a bug will normally always find it important.
>
> Benny

Quite so! :)

Doug



------------------------------------------------------------------------------
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013
and get the hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb
_______________________________________________
Gramps-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-devel
Loading...