On Fri, 2006-04-28 at 11:16 +0200, Christian Stimming wrote: > only one blocker. I'd like to ask everyone to go through the other > (critical, major, normal) bugs and look for ones that *must* be resolved > before 2.0.0. Then mark those as a blocker -- if others think those are > not a blocker for 2.0.0, we can discuss that directly in bugzilla. For > example, http://bugzilla.gnome.org/show_bug.cgi?id=332251 is probably a > blocker as well.
I don't think we should change the status; "blocker" in bugzilla has a specific, different meaning. Targeting them to '2.0.0' should be sufficient: we can track the size of this list. > Because *if* there are only 1-3 blocker issues left right now, IMHO we > will be able to actually make the 2.0.0 release on May 14th, which is > just over two weeks from now! If we decide to do this, we should already > announce that plan in the upcoming 1.9.6-announcement. And those of use Is 1.9.6 also the first (hopefully only) Release Candidate? 2.0.0rc1? Should we do a seperate RC in about a week (May 7th)? Should we bother with RCs at all? All that really matters is that we stop making commits at some point ... when should that point be? I'd say 5/7 ... Wed 5/10 at the latest. -- ...jsled http://asynchronous.org/ - `a=jsled; b=asynchronous.org; echo [EMAIL PROTECTED] _______________________________________________ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
