I'd like to propose 7 Oct 2007 as a tag date for the 2.1.0 version. If anyone would be interested in helping with the build, please don't be shy!
Pursuant to some other discussions, for the 2.1.x series, I renamed the Release Notes to Version Notes, since we also use the word "release" in another sense. We've been putting the "Release Plan" in the notes lately, and for now, I labeled it the "Build/Release Plan", since, as it stands, a "Release Plan" is required by our charter. Again, any help with the build/release would be welcome! For the record, personally, I do not consider the 2.1.x series to be "feature locked". If people want to continue to add new features and conduct refactorings in later 2.0.x milestones, that's fine with me. Of course, as always, any destructive API changes should be subject to the usual deprecate/release/remove protocol. If there are any features or API signatures that we deprecated in 2.0.x that we would like to remove for 2.1.x, this would be a good time to apply the patch! -Ted. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
