You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by kf...@collab.net on 2003/08/26 14:48:31 UTC
Re: svn commit: rev 6876 - in branches: release-0.28 release-0.28.0
pll@tigris.org writes:
> Added:
> branches/release-0.28/
> - copied from rev 6875, branches/release-0.28.0/
> Removed:
> branches/release-0.28.0/
> Log:
> fixed release number to be X.YY
I thought we are always including the patch level now, e.g. "0.28.0".
That's how we did it for 0.27.0...
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: svn commit: rev 6876 - in branches: release-0.28 release-0.28.0
Posted by Ben Collins-Sussman <su...@collab.net>.
cmpilato@collab.net writes:
> There. I said it. I've proven that I can deal with a little chaos in
> my life.
Your newborn baby has finally warped your mind! :-D
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: svn commit: rev 6876 - in branches: release-0.28 release-0.28.0
Posted by Blair Zajac <bl...@orcaware.com>.
cmpilato@collab.net wrote:
>
> Blair Zajac <bl...@orcaware.com> writes:
>
> > I'm not suggesting the tag contents change, just the name of the
> > tag.
> >
> > I also don't believe anybody is using these tag URLs to check out
> > working copies, so there won't be an effect of these being renamed.
>
> Sorry, I use the tags all the time to check out working copies. But
> as for going back and making copies of the tags just for consistency's
> sake ... (watch out, sussman, this answer is going to surprise you) I
> just don't care.
I don't want copies of tags, such as 0.28 and 0.28.0 in the tree, which
would be messy, but just one.
It would be nice for consistency sake, but this is getting a little
bike-shedy.
Blair
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: svn commit: rev 6876 - in branches: release-0.28 release-0.28.0
Posted by cm...@collab.net.
Blair Zajac <bl...@orcaware.com> writes:
> I'm not suggesting the tag contents change, just the name of the
> tag.
>
> I also don't believe anybody is using these tag URLs to check out
> working copies, so there won't be an effect of these being renamed.
Sorry, I use the tags all the time to check out working copies. But
as for going back and making copies of the tags just for consistency's
sake ... (watch out, sussman, this answer is going to surprise you) I
just don't care.
There. I said it. I've proven that I can deal with a little chaos in
my life.
I.
I want my mommy.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: svn commit: rev 6876 - in branches: release-0.28 release-0.28.0
Posted by Blair Zajac <bl...@orcaware.com>.
> Luke Blanshard wrote:
>
> Blair Zajac wrote:
>
> > Michael Wood wrote:
> >
> >
> >> ... I think renaming the tags would be a bit dodgy.
> >>
> >>
> > For what reason? They are just symbolic names after all.
> >
> Because tags aren't supposed to change over time. That is, neither
> their contents nor their names should change: you want someone who's
> still using an old version to be able to refer to that version with the
> tag that they originally used to fetch it. If you rename it, it's as
> good as gone to someone who relied on the old name.
I'm not suggesting the tag contents change, just the name of the tag.
I also don't believe anybody is using these tag URLs to check out
working copies, so there won't be an effect of these being renamed.
Blair
--
Blair Zajac <bl...@orcaware.com>
Plots of your system's performance - http://www.orcaware.com/orca/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: svn commit: rev 6876 - in branches: release-0.28 release-0.28.0
Posted by Luke Blanshard <lu...@blanshard.us>.
Blair Zajac wrote:
>Michael Wood wrote:
>
>
>>... I think renaming the tags would be a bit dodgy.
>>
>>
>For what reason? They are just symbolic names after all.
>
Because tags aren't supposed to change over time. That is, neither
their contents nor their names should change: you want someone who's
still using an old version to be able to refer to that version with the
tag that they originally used to fetch it. If you rename it, it's as
good as gone to someone who relied on the old name.
Luke
Re: svn commit: rev 6876 - in branches: release-0.28 release-0.28.0
Posted by Blair Zajac <bl...@orcaware.com>.
Michael Wood wrote:
>
> On Tue, Aug 26, 2003 at 09:02:58AM -0700, Blair Zajac wrote:
> [snip]
> > I recall a discussion where people agreed to use 0.XX.Y throughout
> > all documentation and tags. Right now they are inconsistent.
> >
> > In fact, I volunteered to rename all the tags to this form in
> > the tree.
> [snip]
>
> Yes, I remember that. I think renaming the tags would be a bit dodgy.
For what reason? They are just symbolic names after all.
Blair
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: svn commit: rev 6876 - in branches: release-0.28 release-0.28.0
Posted by Luke Blanshard <lu...@blanshard.us>.
Michael Wood wrote:
>On Tue, Aug 26, 2003 at 09:02:58AM -0700, Blair Zajac wrote:
>[snip]
>
>
>>I recall a discussion where people agreed to use 0.XX.Y throughout
>>all documentation and tags. Right now they are inconsistent.
>>
>>In fact, I volunteered to rename all the tags to this form in
>>the tree.
>>
>>
>[snip]
>
>Yes, I remember that. I think renaming the tags would be a bit dodgy.
>
But adding new tags that conform to the new scheme would not. Instead
of renaming, just copy.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: svn commit: rev 6876 - in branches: release-0.28 release-0.28.0
Posted by Michael Wood <mw...@its.uct.ac.za>.
On Tue, Aug 26, 2003 at 09:02:58AM -0700, Blair Zajac wrote:
[snip]
> I recall a discussion where people agreed to use 0.XX.Y throughout
> all documentation and tags. Right now they are inconsistent.
>
> In fact, I volunteered to rename all the tags to this form in
> the tree.
[snip]
Yes, I remember that. I think renaming the tags would be a bit dodgy.
--
Michael Wood <mw...@its.uct.ac.za>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: svn commit: rev 6876 - in branches: release-0.28 release-0.28.0
Posted by Blair Zajac <bl...@orcaware.com>.
cmpilato@collab.net wrote:
>
> kfogel@collab.net writes:
>
> > pll@tigris.org writes:
> > > Added:
> > > branches/release-0.28/
> > > - copied from rev 6875, branches/release-0.28.0/
> > > Removed:
> > > branches/release-0.28.0/
> > > Log:
> > > fixed release number to be X.YY
> >
> > I thought we are always including the patch level now, e.g. "0.28.0".
> > That's how we did it for 0.27.0...
>
> 0.27.0 is a deviation from what was the norm. :-(
I recall a discussion where people agreed to use 0.XX.Y throughout
all documentation and tags. Right now they are inconsistent.
In fact, I volunteered to rename all the tags to this form in
the tree.
Blair
--
Blair Zajac <bl...@orcaware.com>
Plots of your system's performance - http://www.orcaware.com/orca/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: svn commit: rev 6876 - in branches: release-0.28 release-0.28.0
Posted by kf...@collab.net.
cmpilato@collab.net writes:
> > I thought we are always including the patch level now, e.g. "0.28.0".
> > That's how we did it for 0.27.0...
>
> 0.27.0 is a deviation from what was the norm. :-(
I think we should keep the patch level; otherwise it's an implied
number, and of course people not familiar with the project won't know
that an implied number is there.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: svn commit: rev 6876 - in branches: release-0.28 release-0.28.0
Posted by cm...@collab.net.
kfogel@collab.net writes:
> pll@tigris.org writes:
> > Added:
> > branches/release-0.28/
> > - copied from rev 6875, branches/release-0.28.0/
> > Removed:
> > branches/release-0.28.0/
> > Log:
> > fixed release number to be X.YY
>
> I thought we are always including the patch level now, e.g. "0.28.0".
> That's how we did it for 0.27.0...
0.27.0 is a deviation from what was the norm. :-(
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org