On Fri, 2006-04-28 at 08:57 -0400, John McNabb wrote: > I have read through the release plan. I can't imagine that we will > have a true code freeze, as there could always be bug fixes that it is > determined must be fixed. A code freeze on features and non-critical > bugs (graphical glitches and the like) makes sense, but fixes to > critical bugs (seg faults, crashing, etc) should not happen until the > actual release.
Agreed. "code freeze" is probably the wrong term here. Feature freeze then bugfix-only is better. > If we have a code freeze of any variety, than I would definitely say > that we should make a branch instead. Even with just a feature > freeze, I would suggest we branch the code at that point. The trunk > should not be our release candidate once we are in a feature freeze. OTOH, holding new development hostage makes devs concentrate on the release. I'd certainly be pretty pissed off at someone who's committing Latest Cool Feature while critical bugs are sitting there unfixed. And if there are really no critical bugs, then we can move the timetable forward. > I have added my hoped for list of features to the feature list. I, of > course, reserve the right to change it up until the 6 May deadline ;) Me too 8) One reason I like the feature list is so we can negotiate: your feature list might make me add/remove things from my feature list. BTW, I've added details to all my points, so they're not open-ended. I'd like to see a description of "gui enhancements"... > I have also added a list for critical BUGS that should be fixed before > we consider the release stable. I initially populated the list based > on the short description, so some of the ones I put in the list > probably aren't really critical, and some BUGS that are critical > probably fell through the cracks. Please revise the list as > appropriate. Of course, if you fix a bug, it can be removed from the > list, although perhaps it should just be noted as FIXED. Great! Perhaps we should also bump the Priority on these to 7:High? Thanks! Rusty. -- ccontrol: http://ozlabs.org/~rusty/ccontrol _______________________________________________ Wesnoth-dev mailing list [email protected] https://mail.gna.org/listinfo/wesnoth-dev
