On 6/21/07, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote:
<snip> as long as something works, I'm not sure why we would exclude it from a
Tuscany release.
I think we need a bit more clarity about what it means to include something in the release. Is it just having the code included in the src distro, or included in the src distro as part of the build, or also included in the binary distro, or included in both distro's along with itests, samples, readme's or web site doc, and mention of the new thing in the release notes?
From the 0.90 release things were pulled out for not being quite there, a
lot of the time spent before the final release artifacts got done was because people reviewing the distro's wanted all things up to a certain standard. Getting all this done can take a lot of work. Last minute changes often cause unexpected blocking problems in the distributions resulting in respins and more delay. If we just include everything "that works" is someone reviewing a release RC going to complain that some new sample is missing a readme, that a demo should have an Ant build script, or that some new extension doesn't even have a sample? If things must be of a certain standard then I don't think its reasonable to expect the release manager to do all the work to get things there. How about: - by default everything is kept in the src distro unless there's some reason not to - only the things mentioned on the release wiki page get included in the build, binary distribution, and mentioned in the release notes - after the brn is cut we need to ask on the ML before adding new things to the wiki release page - adding something to the wiki release page implies some commitment to help get it to the required standard in line with the release schedule. ...ant
