Hey guys, With the completion of Routing in 0.10 we''re rapidly approaching rails-1.0. The three things left to do are: 1) Packaging 2) Performance enhancements 3) Faults 1 & 2 are being looked after at present, however I think #3 could do with a little help. The signal to noise ratio of our trac installation has been degrading lately. There are ''bugs'' which are actually feature requests, ''bugs'' whose behaviour is clearly documented and ''bugs'' without enough information to reproduce or investigate. We also need to start deciding which bugs are going to be fixed for 1.0, and which bugs are to be deferred till post 1.0. After talking with david last night, I''ve decided to take on this ''triage'' responsibility to help get us over the line for 1.0. I''ll be doing 3 things. 1) Resolving bugs which don''t have enough information associated with them (with a comment asking them to re-open if they can provide that information) 2) Setting the milestone to 1.0 for all the bugs which should block 1.0 3) Removing the milestones (setting to '''') for bugs which shouldn''t block 1.0. Now, I''m bound to make some mistakes here, so if you disagree with any changes that I make to your bug just send a (polite) email to the list and we can chat about it here. If anyone wants to help me out with this, just drop me an email and we can coordinate. -- Cheers Koz (nzkoz in #rails)
Michael Koziarski wrote:> > 1) Resolving bugs which don''t have enough information associated with > them (with a comment asking them to re-open if they can provide that > information)Not saying you''re responsible for this, but recently I''ve noticed a few bugs being marked as closed by "anonymous". So, for anyone, please remember to enter your name in the slot when you make changes to a bug, especially if it wasn''t you who originally posted the bug, and especially if you''re marking it as resolved. If any issues come up at a later point, it''s hard (if not impossible) track down who "anonymous" is. It''s easy to forget to enter it because Trac doesn''t require it. Thank you, Michael, for stepping up to this task, it''s something I also think is sorely needed. We can all help to make Michael''s job with this easier by trying to properly mark our requests, leaving at least our names if not our email addresses, and being as clear as possible. Thanks -Scott _______________________________________________ Rails mailing list Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org http://lists.rubyonrails.org/mailman/listinfo/rails
On Tue, 1 Mar 2005 10:41:56 +1300, Michael Koziarski <koziarski-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> Now, I''m bound to make some mistakes here, so if you disagree with > any changes that I make to your bug just send a (polite) email to the > list and we can chat about it here.I''m not sure that all non-anonymous reporters syndicate the Timeline RSS, so they may not know that its getting closed, since the Rails Trac doesn''t send email notifications. But excellent plan Regards Leon