|
View:
New views
6 Messages
—
Rating Filter:
Alert me
|
|
|
Scheduling a Bug DayHello Tomboy team!
I'd like to follow up from our meeting a week and a half ago and schedule a day to go through Tomboy's Bugzilla. The goal would be to review patches in Tomboy's bugzilla, confirm bugs, and work on bug fixes. How does Wednesday, May 6th or Thursday, May 7th work for everyone? Take a look at your calendars, and drop a note to the list. Thanks! Paul _______________________________________________ Tomboy-list mailing list Tomboy-list@... http://lists.beatniksoftware.com/listinfo.cgi/tomboy-list-beatniksoftware.com |
|
|
Re: Scheduling a Bug DayHey,
For me is better after 7th but I can prepare some patches to be committed any day ;-) Everaldo. On Fri, May 1, 2009 at 11:41 PM, Paul Cutler <pcutler@...> wrote: > Hello Tomboy team! > > I'd like to follow up from our meeting a week and a half ago and schedule a > day to go through Tomboy's Bugzilla. The goal would be to review patches in > Tomboy's bugzilla, confirm bugs, and work on bug fixes. > > How does Wednesday, May 6th or Thursday, May 7th work for everyone? > > Take a look at your calendars, and drop a note to the list. > > Thanks! > > Paul > > _______________________________________________ > Tomboy-list mailing list > Tomboy-list@... > http://lists.beatniksoftware.com/listinfo.cgi/tomboy-list-beatniksoftware.com > > Tomboy-list mailing list Tomboy-list@... http://lists.beatniksoftware.com/listinfo.cgi/tomboy-list-beatniksoftware.com |
|
|
Re: Scheduling a Bug DayWe can push it out a week later as well, if people would like more time to prepare.
Paul On Sat, May 2, 2009 at 8:08 AM, Everaldo Canuto <ecanuto@...> wrote: Hey, _______________________________________________ Tomboy-list mailing list Tomboy-list@... http://lists.beatniksoftware.com/listinfo.cgi/tomboy-list-beatniksoftware.com |
|
|
Re: Scheduling a Bug DayOn Fri, May 1, 2009 at 7:41 PM, Paul Cutler <pcutler@...> wrote:
> Hello Tomboy team! > > I'd like to follow up from our meeting a week and a half ago and schedule a > day to go through Tomboy's Bugzilla. The goal would be to review patches in > Tomboy's bugzilla, confirm bugs, and work on bug fixes. > > How does Wednesday, May 6th or Thursday, May 7th work for everyone? > > Take a look at your calendars, and drop a note to the list. This is doable for me, but I wonder if we would get a better turn-out by having the bug day on a weekend? Any thoughts? When do people normally do these? :-) Sandy _______________________________________________ Tomboy-list mailing list Tomboy-list@... http://lists.beatniksoftware.com/listinfo.cgi/tomboy-list-beatniksoftware.com |
|
|
Re: Scheduling a Bug DayI think we should plan how we will tackle this bugday before it begins.
Perhaps set priorities like 1. Test/apply bugs scheduled to 0.15. 2. Triage bugs scheduled to 0.15. 3. Triage the remaining UNCONFIRMED bugs and schedule them to Future or 0.15. A wiki page with planning notes and bugzilla queries would help this along. Ooops. Did I just volunteer myself ??? I'm usually available on Wed or Thurs evenings MST. Weekends are more difficult. _______________________________________________ Tomboy-list mailing list Tomboy-list@... http://lists.beatniksoftware.com/listinfo.cgi/tomboy-list-beatniksoftware.com |
|
|
Re: Scheduling a Bug DayOn Sat, May 2, 2009 at 11:23 AM, Michael Fletcher
<m.fletcher@...> wrote: > I think we should plan how we will tackle this bugday before it begins. Yes, definitely. I'm not comfortable scheduling a bug day without a solid plan first. > Perhaps set priorities like > > 1. Test/apply bugs scheduled to 0.15. > 2. Triage bugs scheduled to 0.15. > 3. Triage the remaining UNCONFIRMED bugs and schedule them to Future or 0.15. > > A wiki page with planning notes and bugzilla queries would help this > along. Ooops. Did I just volunteer myself ??? That is a great idea. Some things we could do: * Test outstanding patches, leave comments on those that no longer apply, follow-up on those that do * Get rid of as many UNCONFIRMED bugs as possible * Schedule them, as Mike suggests * Consider going as far as creating milestones for each upcoming 0.15.x release, and scheduling bugs for each milestone? * Mark gnome-love (if you have a clue about how hard it would be to work on a given bug) * And, of course, looking at old bugs with no recent updates to see if they're still valid Would love to just point people at a wiki page with simple instructions, and have everything go smoothly. Once we know what we're doing, let's schedule a day. :-) And yes, let's do it soon! Sandy _______________________________________________ Tomboy-list mailing list Tomboy-list@... http://lists.beatniksoftware.com/listinfo.cgi/tomboy-list-beatniksoftware.com |
| Free embeddable forum powered by Nabble | Forum Help |