I didn't hear any objections (or a lot of support for that matter <g>)
so let's go with Feb 22 as our target date for Milestone 5.
That means code freeze on Fri Feb 15th and no new features from now on.
If there are problems with those dates speak-up *now* -- we can shift
everything later by a week with no great repercussion.
I'll be away from the keyboard for the last week up to M5, but I'm sure
you won't notice.
Regards,
Tim
Alexey Petrenko wrote:
No objections.
Let's create list of must-fix issues.
SY, Alexey
2008/2/4, Tim Ellison <[EMAIL PROTECTED]>:
As usual, we are all busy putting in new functionality and addressing
bugs in the latest HEAD stream. Let's not forget delivering that
goodness those users who move from milestone to milestone release.
We are getting into the habit now of producing stable, well-tested
milestone builds; and this would be Milestone 5.
How about we aim for Fri February 22nd for the next stable release, with
our usual feature and code chill-down periods?
Regards,
Tim
