[wp-hackers] WordPress stable branch

[Ryan Boren]

On Fri, 2005-06-24 at 01:52 +0200, Mark Rosenstand wrote:
> On Thursday 23 June 2005 23:37, Scott Merrill wrote:
> > Mark Rosenstand wrote:
> > > With everything changing for 1.6, I *really* feel a need for a seperate
> > > stable branch. WordPress is by its interpreted nature a true dream to
> > > keep updated through SVN; but when the DB tables starts changing it
> > > really isn't that much fun any more.
> > >
> > > What are the reasons for not branching, if any?
> >
> > Because the 1.5.1.2 tag exists, and works:
> >   svn co http://svn.automattic.com/wordpress/tags/1.5.1.2
> >
> > That's your stable version.
> 
> But aren't tags permanent? What happens when the next security vulnerability 
> gets discovered in 1.5.x (e.g. 1.5.1.3)? My point being that it is easier to 
> track a branch than to follow the tagging, fetch new tags, replace them, etc.

There isn't any 1.5 development to track at the moment.  If we need to
do 1.5.1.3, we can create a 1.5 branch from the 1.5.1.2 tag.  Basically,
I haven't created a branch because we haven't needed to commit anything
for the 1.5 series.  Every commit since 1.5.1.2 has been for 1.6.

Ryan