Quantcast

bug triage

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

bug triage

Paul Franklin-5
I wonder if somebody could summarize or explain
the bug triage process.  Is it automated?  Is there
a czar?  Is it voluntary (signing up to fix a bug)?  Is
it by type?  Is it time driven (weekly? monthly?)?
Etc.  Thanks.

------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
lucky parental unit.  See the prize list and enter to win:
http://p.sf.net/sfu/thinkgeek-promo
_______________________________________________
Gramps-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: bug triage

Stéphane Charette-2
We're *very* informal in our process.  If you have a bug you'd like someone to fix, you mention it on the mailing list, and maybe if one of the devs has time it will be picked up.  If you have some python skills and want a shot at a bug, create an account for yourself on the bug site, assign the bug to yourself, and add comments or attach a patch and then bring it up on the dev mailing list to be reviewed.  Typically bugs are not assigned directly to another developer.  It is up to developers to decide how much time they have, and to take ownership of things they plan on fixing.

When something critical is found/fixed, we then tend to pay closer attention to how much has been recently fixed, and if there are remaining items we'd like to have before a release.  Otherwise we don't normally have regular bug scrubs, assign tickets to specific releases, or to overly-restrict svn checkins.  (Everything in moderation of course.)  Release planning is done publicly on the gramps-devel mailing list.

In the last few years we typically had about 1 release per quarter.  This year there have been a few more than that.  I don't think we currently have hard plans as to when the next release will be made available.

Stéphane Charette


On Tue, Jun 8, 2010 at 20:55, Paul Franklin <[hidden email]> wrote:
I wonder if somebody could summarize or explain
the bug triage process.  Is it automated?  Is there
a czar?  Is it voluntary (signing up to fix a bug)?  Is
it by type?  Is it time driven (weekly? monthly?)?
Etc.  Thanks.

------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
lucky parental unit.  See the prize list and enter to win:
http://p.sf.net/sfu/thinkgeek-promo
_______________________________________________
Gramps-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-users


------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
lucky parental unit.  See the prize list and enter to win:
http://p.sf.net/sfu/thinkgeek-promo
_______________________________________________
Gramps-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: bug triage

Benny Malengier


2010/6/9 Stéphane Charette <[hidden email]>
We're *very* informal in our process.  If you have a bug you'd like someone to fix, you mention it on the mailing list, and maybe if one of the devs has time it will be picked up.  If you have some python skills and want a shot at a bug, create an account for yourself on the bug site, assign the bug to yourself, and add comments or attach a patch and then bring it up on the dev mailing list to be reviewed.  Typically bugs are not assigned directly to another developer.  It is up to developers to decide how much time they have, and to take ownership of things they plan on fixing.

When something critical is found/fixed, we then tend to pay closer attention to how much has been recently fixed, and if there are remaining items we'd like to have before a release.  Otherwise we don't normally have regular bug scrubs, assign tickets to specific releases, or to overly-restrict svn checkins.  (Everything in moderation of course.)  Release planning is done publicly on the gramps-devel mailing list.

In the last few years we typically had about 1 release per quarter.  This year there have been a few more than that.  I don't think we currently have hard plans as to when the next release will be made available.


I would aim for a spring release of 3.3, so a yearly major release (3.1 and 3.2 where also in the spring). It looks like most people have a coupe of months they can program in their free time, but those months are not in the same season.
Gramps is a group effort, bug triage is done by all developers when time permits it. Obviously, blocking bugs, when noticed, are fixed almost immediately.

Benny
 
Stéphane Charette



On Tue, Jun 8, 2010 at 20:55, Paul Franklin <[hidden email]> wrote:
I wonder if somebody could summarize or explain
the bug triage process.  Is it automated?  Is there
a czar?  Is it voluntary (signing up to fix a bug)?  Is
it by type?  Is it time driven (weekly? monthly?)?
Etc.  Thanks.

------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
lucky parental unit.  See the prize list and enter to win:
http://p.sf.net/sfu/thinkgeek-promo
_______________________________________________
Gramps-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-users


------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
lucky parental unit.  See the prize list and enter to win:
http://p.sf.net/sfu/thinkgeek-promo
_______________________________________________
Gramps-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-users



------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
lucky parental unit.  See the prize list and enter to win:
http://p.sf.net/sfu/thinkgeek-promo
_______________________________________________
Gramps-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: bug triage

Paul Franklin-5
In reply to this post by Stéphane Charette-2
On 6/9/10, Stéphane Charette <[hidden email]> wrote:
> ... If you have a bug you'd like someone to fix, you mention it ...

http://www.gramps-project.org/bugs/view.php?id=4010 is
"Descendant Tree graphical report shows first marriage always"

Thanks in advance ...

------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
lucky parental unit.  See the prize list and enter to win:
http://p.sf.net/sfu/thinkgeek-promo
_______________________________________________
Gramps-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-users
Loading...