Re: cvs: pear-core / package-PEAR.xml package2.xml /PEARChannelFile.php Common.php Config.php DependencyDB.php Installer.php PackageFile.phpPackager.php Registry.php Remote.php /PEAR/PackageFile v1.php /PEAR/PackageFile/Generatorv2.php /PE

Greg Beaver wrote:

> bertrand Gugger wrote:
>  
>
> > Greg Beaver wrote:
> >
> >    
> >
> > > cellog        Sat Mar 25 21:09:09 2006 UTC
> > > <release>
> > > -  <version>1.4.8</version>
> > > -  <date>2006-03-06</date>
> > > +  <version>1.5.0a1</version>
> > > +  <date>2006-05-01</date>
> > >  <license>PHP License</license>
> > > -  <state>stable</state>
> > > +  <state>alpha</state>
> > >
> > >
> > >      
> > Really ? for the "holly workers" feast ?
> >
> > A question, how are MTH organized ?
> > I guess it's when some intermediate stable is reached...
> > Is it reported ?
> >
> > I know, this question is somewhat late, nobody intends to count after 9 :)
> >    
>
> Is May 1 the holly workers feast?  The things you learn ;)
>
> As was discussed on pear-core@xxxxxxxxxxxxx, the pear-core/ directory in
> CVS has been branched.
>
> PEAR 1.4.x -> PEAR_1_4 branch
> PEAR 1.5.0 -> HEAD
>
> This commit was in HEAD.  It does not preclude a 1.4.10 release if
> necessary.  May 1 is an arbitrary date, but expresses the expedited
> timeline (I don't want to see a year go by before this release as it is
> a minor feature addition)
>
> Greg
>
>  
I get it.
I see this 1.5.0 release as a closing time for 1.3.x serie
and as opening some only bug fix one for 1.4.x

My question was about how merges to head are organized.

I can understand that 10 not necessarly follows 9.
Regards
--
toggg