[wp-hackers] WordPress 18.104.22.168 SVN tag please?
false.hopes at gmail.com
Wed Jun 29 18:20:41 GMT 2005
My point was that tagging isn't really needed if there are to be no
more changes in the branch, which I thought would be the case at the
time of 22.214.171.124
On 6/29/05, Ryan Boren <ryan at boren.nu> wrote:
> On Wed, 2005-06-29 at 13:20 -0400, David Chait wrote:
> > I disagree. You should always tag when there is some sort of release, so
> > there's never a question of what that release was in files and time. And
> > tags in SVN are near-zero overhead (they just point to the revision number
> > if I recall a year ago!). Go tag happy! ;) It also has the secondary
> > advantage of being able to look at the tags as a history/status of its own,
> > rather than looking at individual branches and checkins...
> I'll tag when I get home. Right now I'm stuck in a meeting.
> "Do we support section blah.blah.blah of the OMG spec? The customer
> demands that we support section blah.blah.blah."
> "Does the customer even know what section blah.blah.blah means?"
> "No, but they think it sounds cool and they want it."
> Anyway, for the moment 126.96.36.199 is known as repository revision 2672.
> > ----- Original Message -----
> > From: "Robert Deaton" <false.hopes at gmail.com>
> > To: <wp-hackers at lists.automattic.com>
> > Sent: Wednesday, June 29, 2005 10:14 AM
> > Subject: Re: [wp-hackers] WordPress 188.8.131.52 SVN tag please?
> > There is no reason for a tag unless there is something newer, just use
> > the 1.5 branch.
> > On 6/29/05, Brian Dupuis <wordpress at coldforged.org> wrote:
> > > Matt/Ryan,
> > >
> > > Could we get an SVN tag on the 184.108.40.206 release files? Is there a reason
> > > that this isn't part of the standard process in performing releases?
> > _______________________________________________
> > wp-hackers mailing list
> > wp-hackers at lists.automattic.com
> > http://lists.automattic.com/mailman/listinfo/wp-hackers
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
More information about the wp-hackers