[wp-hackers] Latest 2.1.x release when not yet tagged

Robin Adrianse robin.adr at gmail.com
Tue Apr 3 13:19:08 GMT 2007

The 2.1 branch isn't necessarily 2.1.3, but it doesn't get any dangerous (
i.e. stuff that could break things) commits -- just bug fixes. You're
probably pretty safe running off of the 2.1 branch. I may be wrong, though.

On 4/3/07, Daniel Jalkut <jalkut at red-sweater.com> wrote:
> I've noticed the past couple releases I've jumped the gun in response
> to release announcements, trying to "svn export" from a tagged
> directory, before it exists.
> While I'd like to suggest that tags always be made coincidental with
> the packaging and releasing of a version, I know that it's not easy
> to be perfect :)
> So in cases where there is no tag yet, is it safe to assume that the
> latest revision of the appropriate branch is in fact the same as the
> release? For instance, is
> http://svn.automattic.com/wordpress/branches/2.1/
> Currently 2.1.3? Or is there a trickier voodoo going on?
> Thanks,
> Daniel
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers

More information about the wp-hackers mailing list