[wp-hackers] On Subversion and 2.5.x-alpha not being in Trunk

[DD32]

Does SVN have any inbuilt aliasing functionality?

A different branch could be created, and every time a release is made, its  
commited into that branch as well, but that seems a bit much of an extra  
step to me.
So is it possible to setup a alias so that /branch/stable/  =>  
/tags/2.5.1, and that a quick update could set it to 2.5.2?

If SVN doesnt(I couldnt see much on a quick google), Could the  
svn:external property be used instead? ie. /branches/stable/ has the  
property of svn:external tags/2.5.1, Any checkoutof /branches/stable would  
pull in /tags/2.5.1, and then any updates would be able to pull in the  
other branch.. Or is that not possible with the way svn:external works?

I'm just rambling out loud, I think a "Latest stable release" tag/branch  
could be of great use to many people, but i dont know enough about svn's  
internals to know exactly how it'd work.

On Fri, 16 May 2008 12:45:06 +1000, Eric Marden <wp at xentek.net> wrote:

> On May 14, 2008, at 5:11 PM, Jeremy Visser wrote:
>
>> On Wed, 2008-05-14 at 14:02 -0700, Aaron D. Campbell wrote:
>>> I have a lot of WordPress installs that I manage, and it would
>>> be nice to just set a cron job to "svn up" every day (or once a week,
>>> etc). There is a trac ticket asking for a stable tag like phpMyAdmin
>>> does: http://trac.wordpress.org/ticket/3593
>>
>> I do that on a project of mine, and it's a pain in the butt to work.
>
>
> Please go on. I'd like to see the reasoning behind not having a stable
> tag that represents the same revision as /tags/2.5.1, etc?
>
> Its trivial create two tags, one for the named version, and one for
> the standing 'production/stable' tag. And given that WP doesn't
> release a build lightly, it seems like it would add very little
> overhead to whatever the existing process is. And if the process is
> automated, then the overhead would be barely non-existent.
>
> -e
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>