1. I took all bugs in the 3.0.0 tracker bug and made sure all have a
milestone release of 3.0.0. Using milestones is much easier to query
and track, especially as the list of bugs grew and grew and grew.
2. I added a 3.0.1 milestone.
3. I propose we enter Review-then-Commit mode for HEAD on Monday morning
at 0900 UTC. That should be enough time to cycle everything out of
70_testing.cf, including some network tests that I need to add (NJABL
has a new dynamic list I want us to test) before this weekend.
4. All developers and bug editors, please review those bugs that remain
in the 3.0.0 queue (that is, those bugs with a 3.0.0 milestone). We
should change bugs as appropriate to have a 3.0.1 or 3.1.0 milestone.
Here are the general criteria I propose:
major bugs stay in 3.0.0
minor bugs move to 3.0.1
optional/big changes move to 3.1.0
Later, things can be moved to earlier releases as code is completed
and fully tested.
5. We release 3.0.0-pre1 in one week to have more people start testing
it. It already has better accuracy for both FPs and FNs than 2.63.
Daniel
--
Daniel Quinlan
http://www.pathname.com/~quinlan/
