You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Tobias Ringstrom <to...@ringstrom.mine.nu> on 2003/08/26 20:26:07 UTC
The CHANGES file
Paul Lussier wrote:
> ------------------------------------------------------------------------
> rev 6856: pll | 2003-08-25 11:10:24 -0400 (Mon, 25 Aug 2003) | 1 line
>
> * CHANGES - updated release number...again
> ------------------------------------------------------------------------
Right now the version line in the CHANGES file looks like this:
Version x.y.z (released <date>, rev 9999, branches/release-x.y.z)
Why is the CHANGES file referring to a branch and not a tag? There's
also the revision number of the repostitory, which of course makes
sense since it refers to a branch. If a tag is referred to instead of
a branch, the revision number becomes irrelevant. [I assume of course
that the tags are not modified after they are created.]
I propose to change the string "rev 9999, branches/release-x.y.z" to
the full URL of the tag ("http://svn.collab.net/repos/svn/tags/x.y.z")
instead. I believe that such a change would remove the most magical
step from the release process, and therefore make things a tiny bit
easier for the release manager. I also think that it would be very
cool to be able to cut-and-paste the URL directly from the CHANGES file.
What do you think?
/Tobias
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: The CHANGES file
Posted by Paul Lussier <pl...@lanminds.com>.
On Wed, 2003-08-27 at 11:52, cmpilato@collab.net wrote:
> Actually, I like you proposal. The branch/rev combination doesn't
> mean squat in my opinion -- just give the URL of the tag and be done
> with it.
FWIW, if I ever get the release out the door, I've added a line
underneath with the URL to the tag. Next release I'll only use the tag
URL...
--
Seeya,
Paul
GPG Key fingerprint = 1660 FECC 5D21 D286 F853 E808 BB07 9239 53F1 28EE
If you're not having fun, you're not doing it right!
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: The CHANGES file
Posted by Tobias Ringstrom <to...@ringstrom.mine.nu>.
cmpilato@collab.net wrote:
> Hm, such serious response to a non-serious post. :-)
Heh. I promise not to take your posts seriously from now on. ;-)
Actually, I suspect from people's reactions here and elsewhere that I
often sound a lot more serious and aggressive when I express myself in
written English than I intend to. But I guess it would be even worse if
I wrote in Swedish instead... :-)
/Tobias, nice guy wanna-be
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: The CHANGES file
Posted by cm...@collab.net.
Tobias Ringstrom <to...@ringstrom.mine.nu> writes:
> cmpilato@collab.net wrote:
> > Tobias Ringstrom <to...@ringstrom.mine.nu> writes:
> >
> >>Why is the CHANGES file referring to a branch and not a tag?
> > Because at the time the CHANGES file is edited, there is no tag. And
> > after the tag is created, you can't edit the CHANGES file (duh, it's a
> > tag). :-)
>
> I could say that at the time the CHANGES file is edited, you do not
> know what the repository revision will be when you commit the
> change.
Hm, such serious response to a non-serious post. :-)
Actually, I like you proposal. The branch/rev combination doesn't
mean squat in my opinion -- just give the URL of the tag and be done
with it.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: The CHANGES file
Posted by Michael Wood <mw...@its.uct.ac.za>.
On Wed, Aug 27, 2003 at 09:28:15AM +0200, Tobias Ringstrom wrote:
> cmpilato@collab.net wrote:
> >Tobias Ringstrom <to...@ringstrom.mine.nu> writes:
> >
> >>Why is the CHANGES file referring to a branch and not a tag?
> >
> >Because at the time the CHANGES file is edited, there is no tag. And
> >after the tag is created, you can't edit the CHANGES file (duh, it's a
> >tag). :-)
>
> I could say that at the time the CHANGES file is edited, you do not
> know what the repository revision will be when you commit the change.
>
> The difference is that you *know* what the tag name will be, but you
> have to *guess* the repository revision. Sure, if the repository is
> lightly used, and you are a fast typer, you will probably guess right,
> but come on. Guess? That does not feel right. In my world, knowing
> beats guessing.
+1
> I also think that referring to a tag is better than referring to a
> branch+revision for a number of other reasons:
>
> 1. It's a single thing, not two.
>
> 2. You can browse the code using a normal web browser. The branch
> is deleted from HEAD when the tag is created.
+1
> 3. It's conceptually better. The tag is what's interesting, and
> the branch is only a "tool" to create the tag.
+1
> But it's not the end of the world of course. :-)
:)
--
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: The CHANGES file
Posted by Paul Lussier <pl...@lanminds.com>.
On Wed, 2003-08-27 at 03:28, Tobias Ringstrom wrote:
> cmpilato@collab.net wrote:
> > Tobias Ringstrom <to...@ringstrom.mine.nu> writes:
> >
> >>Why is the CHANGES file referring to a branch and not a tag?
This has been asked before, but I don't recall it ever being answered :)
> > Because at the time the CHANGES file is edited, there is no tag. And
> > after the tag is created, you can't edit the CHANGES file (duh, it's a
> > tag). :-)
>
> I could say that at the time the CHANGES file is edited, you do not
> know what the repository revision will be when you commit the change.
+1!
> I also think that referring to a tag is better than referring to a
> branch+revision for a number of other reasons:
+1!
>
> 1. It's a single thing, not two.
>
> 2. You can browse the code using a normal web browser. The branch
> is deleted from HEAD when the tag is created.
>
> 3. It's conceptually better. The tag is what's interesting, and
> the branch is only a "tool" to create the tag.
+1, +1, +1 :)
--
Seeya,
Paul
GPG Key fingerprint = 1660 FECC 5D21 D286 F853 E808 BB07 9239 53F1 28EE
If you're not having fun, you're not doing it right!
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: The CHANGES file
Posted by Tobias Ringstrom <to...@ringstrom.mine.nu>.
cmpilato@collab.net wrote:
> Tobias Ringstrom <to...@ringstrom.mine.nu> writes:
>
>>Why is the CHANGES file referring to a branch and not a tag?
>
> Because at the time the CHANGES file is edited, there is no tag. And
> after the tag is created, you can't edit the CHANGES file (duh, it's a
> tag). :-)
I could say that at the time the CHANGES file is edited, you do not
know what the repository revision will be when you commit the change.
The difference is that you *know* what the tag name will be, but you
have to *guess* the repository revision. Sure, if the repository is
lightly used, and you are a fast typer, you will probably guess right,
but come on. Guess? That does not feel right. In my world, knowing
beats guessing.
I also think that referring to a tag is better than referring to a
branch+revision for a number of other reasons:
1. It's a single thing, not two.
2. You can browse the code using a normal web browser. The branch
is deleted from HEAD when the tag is created.
3. It's conceptually better. The tag is what's interesting, and
the branch is only a "tool" to create the tag.
But it's not the end of the world of course. :-)
/Tobias
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: The CHANGES file
Posted by cm...@collab.net.
Tobias Ringstrom <to...@ringstrom.mine.nu> writes:
> Paul Lussier wrote:
> > ------------------------------------------------------------------------
> > rev 6856: pll | 2003-08-25 11:10:24 -0400 (Mon, 25 Aug 2003) | 1 line
> > * CHANGES - updated release number...again
> > ------------------------------------------------------------------------
>
> Right now the version line in the CHANGES file looks like this:
>
> Version x.y.z (released <date>, rev 9999, branches/release-x.y.z)
>
> Why is the CHANGES file referring to a branch and not a tag?
Because at the time the CHANGES file is edited, there is no tag. And
after the tag is created, you can't edit the CHANGES file (duh, it's a
tag). :-)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org