On Mon, Jan 15, 2007 at 10:56:15PM +0000, Justin Mason wrote: > ok. so something like this? > > - T + 0 days: issue prerelease. announce a heads-up mail. clean up our > corpora, get ready for mass-checking, try out mass-check to spot any > big memory leaks or whatnot, fix remaining bugs that affect > mass-checks (esp bug 5260!), get people signed up, enable all rules in > svn. > > - T + 1 week, around a Thursday or so: start --bayes --net mass-checks. > > - T + 3 weeks, a Monday or so: hopefully finish mass-checks, bugs > allowing ;) (note that includes two weekends.) > > - T + 3 weeks: perceptron runs, voting on new proposed scores, etc. > how's about C-T-R once the new scores are applied? then final > RC set of releases... > > - T + N weeks: once we are happy with an RC (so N could be any number > > 3), redo that RC as a full release.
Sure. +1.
Now we have the fun of trying to figure out when "T" is. :)
--
Randomly Selected Tagline:
"I can shoot the manager while I'm at it ... kind of like a bonus."
- Shawshank Redemption
pgp6k6Z0ep1Ep.pgp
Description: PGP signature
