[wp-hackers] WordPress stable branch
ryan at boren.nu
Fri Jun 24 01:03:48 GMT 2005
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 126.96.36.199 tag exists, and works:
> > svn co http://svn.automattic.com/wordpress/tags/188.8.131.52
> > 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. 184.108.40.206)? 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 220.127.116.11, we can create a 1.5 branch from the 18.104.22.168 tag. Basically,
I haven't created a branch because we haven't needed to commit anything
for the 1.5 series. Every commit since 22.214.171.124 has been for 1.6.
More information about the wp-hackers