[wp-hackers] On Subversion and 2.5.x-alpha not being in Trunk
wordpress at dd32.id.au
Fri May 16 12:33:59 GMT 2008
On Fri, 16 May 2008 22:25:02 +1000, John Blackbourn
<johnbillion+wp at gmail.com> wrote:
> Ok let's take this from a different angle.
> The problem here is that 2.5.x development is taking place inside
> /branches/2.5 while 2.6 is in /trunk.
> Really, 2.5.x development should be moved from /branches/2.5 to
> another location so /branches/2.5 acts just as /branches/2.3 and /2.2
> and /2.1 does.
> How were updates to 2.3 being handled while 2.5 development was in
> trunk? That's the model that needs to be mirrored here AFAICS.
By being commited to /branches/2.3 just as is happening at current with 2.5
If you look through the commit log, You'll see that /branches/2.3/ allways
contained the latest dev code for that branch, /brances/2.3 was never
"latest stable" mearly the code which would be used for the next 2.3.x
Changes have been made against /trunk/ and if tested OK, then backported
into the /branches/2.5/ branch, just as has been done in the past.
The only code on svn that is *Allways* the same, is what resides inside
the /tags/ folder, nothing once tagged should change, /branches/*/
contains the latest code for that branch, And /trunk/ contains the latest
code which will have bugs (/branches/*/ will also have bugs most likely as
Looking back over the commit logs, /branches/ has allways been latest code
for a set branch, its never been static between builds, So i'm not sure
where the original suggestion that /branches/2.3/ or /branches/2.2/ were
> On Fri, May 16, 2008 at 1:07 PM, Dan Coulter <dan at dancoulter.com> wrote:
>> On Wed, May 14, 2008 at 4:12 PM, Daniel Torreblanca
>> <regulatethis at gmail.com>
>>> If someone wants to avoid the hassle of typing in a url after "svn
>>> switch" I'd recommend a shell script that takes the version number as
>>> an argument... i.e. "upgrade_wp 2.x", which would then run "svn
>>> switch" with the appropriate URL.
>> FWIW here's the bash script I was using on my last host:
>> Just name the file something then append the version number as an
>> just like Daniel's example above. You can add as many blog paths as you
>> like. I'm not using that on my new host, but it's essentially the same
>> method, I'm just using a CLI PHP script that crabs a list of blogs to
>> upgrade from a database table.
>> Dan Coulter
>> Hey, I got nothing to do today but smile
>> -Simon and Garfunkel
>> wp-hackers mailing list
>> wp-hackers at lists.automattic.com
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
More information about the wp-hackers