On 8/9/07, ant elder <[EMAIL PROTECTED]> wrote: > > I guess early the following week still leaves time for an August release. > It will be real tight though so we'll all need to be quick and thorough > with > our RC reviews as one problem once we get to the IPMC voting and it could > easily slip it into September. > > So does taking the branch on the 21st sound ok to everyone? > > ...ant > > On 8/9/07, Simon Nash <[EMAIL PROTECTED]> wrote: > > > > Ant talked about cutting the branch very early next week. I'd prefer > > that to doing it on August 18th. I will be away for a few days, > > returning home late on the 18th, and I could take advantage of the > > extra couple of days to help with last-minute things. > > > > Simon > > > > Venkata Krishnan wrote: > > > > > Hi, > > > > > > Theres been lots of discussion. So let me summarize my understanding > > > / imaginiation : - > > > > > > - We will cut a branch around Aug 18th for Release 0.95. As always, > > > once the branch is cut we need to be watchful on the commits > > > (including getting the RMs nod to significant ones) to the branch and > > > also ensure the trunk is always in sync. > > > - Post 0.95, maybe a couple of weeks after the release, we'd cut > > > another branch and head with that for 1.0 release. Being a 1.0 > > > release, we prob. need a branch early as that so that we can whet the > > > things we are targetting for the release. > > > > > > Is that all right ? > > > > > > - Venkat > > > > > > > > > > > > On 8/9/07, ant elder <[EMAIL PROTECTED]> wrote: > > > > > >>On 8/9/07, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote: > > >> > > >><snip> > > >> > > >>Sure, 1.0 development should happen in trunk, but I was trying to > > >> > > >>>respond to a different point brought up by Raymond. > > >>> > > >>>On Aug 18, we are going to cut the August release branch. The point > is > > >>>about allowing small changes, bug fixes and improvements to continue > in > > >>>that branch while we are putting the release distros together, with > the > > >>>following conditions: > > >>> > > >>>- No completely new function, only bug fixes and improvements. > > >>>- No changes to dependencies or structure of the distro (unless > > required > > >>>to fix a major bug, and approved by the RM). > > >>>- Commits go with a full build of the runtime, itests, samples and > > demos, > > >>>and verification that the samples still work following the steps > > documented > > >>>in their readmes. > > >> > > >> > > >>Sure ok, the branch wont be immediately frozen, but, and its a big > but, > > we > > >>need to be really careful with that as every time we've allowed > > development > > >>to continue in the branch it has ended up delaying a release. No one > can > > on > > >>each commit do a full review including running all the samples, > reading > > all > > >>the readme's and vetting all the legal stuff, so things get missed. > Its > > also > > >>hard to review things thoroughly after you've already done a review a > > couple > > >>of times, so things start getting missed. I'd rather delay taking the > > branch > > >>than plan on being able to continue development in the branch. There's > > been > > >>a lot of change in trunk since 0.91, maybe what we should do is start > > the > > >>clean up work, legal review, sorting out the distributions for all the > > >>module changes etc in trunk towards then end of next week but not take > > the > > >>branch till very early the following week with the expectation of > > getting > > >>RC1 out really quickly. > > >> > > >> ...ant > > >> > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > +1 for 21st as the target. Can I suggest we take some time (assuming there is some) on the 20th to test the samples and check through the readmes etc before taking the branch.
Simon
