Hi, whether to drop it/name it differently doesn't really fix anything. You need to sync at some point. I personally prefer to work on the branch, since that will get the attention of QA and RC processes and after release, merge everything into HEAD. But that would require, that HEAD remains virtually untouched and is probably not realistic.
What's more important IMO, is what snapshot will be built from which branch? Is the 4.2 tree now officially dead? Ie - what do we tell the users? Related to that: if you fix something now, that also impacts 4.2 tree, should you merge it down, creating the situation where you maintain 3 trees. At 10:54 6-10-2002, Zeev Suraski wrote: >I think that given the circumstances, we should scratch the 4.3 branch and >stick to the main branch for this particular release, at least until we're >very close to the release itself. The vast majority of CVS traffic going >on these days is bug fixes anyway, so creating the branch only makes it >more difficult to keep up - you have to keep the two branches in sync. > >Issuing a request for people not to develop new features for a couple of >months (or telling them to develop in some -dev branch), will, in my >opinion, work better than our conventional release process. I'm very >worried about sync problems with 4.3. > >Zeev > > >-- >PHP Development Mailing List <http://www.php.net/> >To unsubscribe, visit: http://www.php.net/unsub.php > > > Met vriendelijke groeten / With kind regards, Webmaster IDG.nl Melvyn Sopacua -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
