Re: Bugs clearance
Florent André <[email protected]>
| Newsgroups | gmane.comp.cms.lenya.devel |
|---|---|
| Message-ID | <[email protected]> |
On Wed, 21 Jul 2010 10:25:13 -0500, Richard Frovarp <[email protected]> wrote: > On 07/21/2010 10:14 AM, Florent André wrote: >> How to close 157 bugs ? [[..]] >> >> > > I don't know if we want to go about closing bugs in that manner exactly. > Certainly if there is something in the bug asking for validation, or to > check if it was fixed they should be closed. Many of them, are for 1.X version... personally I don't have knowledge and time to check this. Someone can take care of this ? If yes, cool ! says and do... if no, close is a solution. Close have this advantage to send a mail on the list and maybe wake up some reactions. Remember that there is more than 3 years and one version with no actions one them... This couldn't says that there is no more support on 1.X version, but that we restart on a clean state. > > I was thinking something about the 5 bugs a day as well. > > A lot of them are enhancements. I have added a 3.0.0 version number that > we could use. I don't know if it makes more sense to have the > enhancements (without a patch) in Bugzilla or in the Wiki. WDOT? Yes, I think about a 3.0 versions in bugzilla, but IMO do this will not be very clean... As we don't know exactly the limits of 3 fill tickets about it is a little bit strange and could be not well define in the next version context... Regroup all this idea on the wiki will help to have a global view of features needed (with always the link to the original ticket). And when L3 begin to live, create a new bug about the enhancement in the wiki and make it alive with the progress of implementation. > > One other thing we could do is limit the number of bugs shown by the > query from our site to just the current branch or something. Sure, but it's just hiding things, and I'm not really for that. Restart from a clean state is more cool I think and more motivating for bug's take care. Just my two cents. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected]