Today is feature freeze (noon eastern time). Just to clarify for anyone who is not sure what this means, at this point we will punt Contributors sometimes use the verb "punt" when talking about a ticket. This means it is being pushed out to a future release. This typically occurs for lower priority tickets near the end of the release cycle that don't "make the cut." In this is colloquial usage of the word, it means to delay or equivocate. (It also describes a play in American football where a team essentially passes up on an opportunity, hoping to put themselves in a better position later to try again.) all remaining tickets for enhancements and feature requests against the 3.0 milestone that have not been put in yet. There will continue to be fixes to enhancements and feature requests that have already made it in. In some cases, the ongoing coding will be a continuation of the new feature, such as creating an accessible version of the new menus. For others it will just be fixing known flaws. As of freeze, there should no longer be philosophical discussions on tickets for 3.0 features. New tickets should be opened for individual bugs.
If you look at the project schedule, there are 2 weeks allotted between freeze and beta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process.. This is to that we can do a review of what’s been committed, and fix both known bugs and do some UI User interface cleanup that couldn’t be done while the main development of a new feature was going on. If we get to the March 11 and we don’t feel that trunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision. is going to be ready for a public beta yet, we’ll discuss whether the date needs to be pushed or whether we can start the public beta and just post a list of known issues to mitigate problems (I vote for latter). The beta period we have scheduled is about a month long, so I’d rather stay on schedule if possible, and just plan on doing beta 1, 2, etc with a list of known issues published with each.
After freeze is official, I’ll start the final UI review, and will make tickets for things I find as well as posting the list of stuff here.
