8:54 a.m.
Greeting All!
As of now I see
r21-5-latest-beta: 1.305
for version.sh, which says:
#!/bin/sh
emacs_is_beta=t
emacs_major_version=21
emacs_minor_version=5
emacs_beta_version=10
xemacs_codename="burdock"
xemacs_extra_name=
emacs_kit_version=
infodock_major_version=4
infodock_minor_version=0
infodock_build_version=8
I would expect it to be
emacs_beta_version=11
by now, no?
--
Adrian Aichner
mailto:adrian＠xemacs.org
http://www.xemacs.org/
9:03 a.m.
>>>> "APA" == Adrian Aichner
<adrian(a)xemacs.org> writes:
Never mind, this was an off-by-one error on my part :-)
But how does the r21-5-latest-beta tag work anyway?
How is it updated and where does it point to (latest sources or latest
beta release sources)?
Adrian
APA> Greeting All!
APA> As of now I see
APA> r21-5-latest-beta: 1.305
APA> for version.sh, which says:
APA> #!/bin/sh
APA> emacs_is_beta=t
APA> emacs_major_version=21
APA> emacs_minor_version=5
APA> emacs_beta_version=10
APA> xemacs_codename="burdock"
APA> xemacs_extra_name=
APA> emacs_kit_version=
APA> infodock_major_version=4
APA> infodock_minor_version=0
APA> infodock_build_version=8
APA> I would expect it to be
APA> emacs_beta_version=11
APA> by now, no?
APA> --
APA> Adrian Aichner
APA> mailto:adrian＠xemacs.org
APA> http://www.xemacs.org/
--
Adrian Aichner
mailto:adrian＠xemacs.org
http://www.xemacs.org/
12:16 p.m.
|--==> "APA" == Adrian Aichner <adrian(a)xemacs.org> writes:
APA> But how does the r21-5-latest-beta tag work anyway?
It is just a moving "sticky" tag.
APA> How is it updated
By yours truly. :-) Usually after my 6th or 7th coffee for the day I
might say "lets release a beta, just for kicks..."[1]. After I've
cleaned up my workspace and committed the ChangeLogs, CHANGES.beta,
version.sh etc, I'll tag the tree.
First: cvs tag r21-5-x
Then: cvs tag -F r21-5-latest-beta
All the magic is in the '-F'. It 'F'orces files to be tagged with
this tag even if a previous version of the file already has a tag of
the same name.[2]
Because it is "sticky" if you do a 'cvs up' in a working directory that
was checked out with 'cvs co -r r21-5-latest-beta xemacs', nothing will
get updated in your working directory until I move the tag ('cvs tag
-F...') to the next release.
Is that nifty or what? :-)
APA> and where does it point to (latest sources or latest
APA> beta release sources)?
Latest beta release sources. In other words, the contents of
'xemacs-21.5.10.tar.gz' on ftp.xemacs.org is more or less identical to
what the current r21-5-latest-beta tag points to in CVS.
Does that clear it up for you, Adrian? If not, just yell.
Footnotes:
[1] For those who are worried, I don't make the decision that way,
normally I wait until the 10th coffee. :-)
[2] Files in CVS can only have unique tag names.
--
|---<Steve Youngs>---------------<GnuPG KeyID: 10D5C9C5>---|
| XEmacs - It's not just an editor. |
| It's a way of life. |
|------------------------------------<youngs(a)xemacs.org>---|
2:50 p.m.
>>>> "SY" == Steve Youngs
<youngs(a)xemacs.org> writes:
SY> |--==> "APA" == Adrian Aichner <adrian(a)xemacs.org> writes:
APA> But how does the r21-5-latest-beta tag work anyway?
SY> It is just a moving "sticky" tag.
APA> How is it updated
SY> By yours truly. :-) Usually after my 6th or 7th coffee for the day I
SY> might say "lets release a beta, just for kicks..."[1]. After
I've
Oh, in that case you need to put your coffee statistics up under
http://www.xemacs.org/coffee/ so that the beta community can track the
tagging progress.
SY> cleaned up my workspace and committed the ChangeLogs, CHANGES.beta,
SY> version.sh etc, I'll tag the tree.
SY> First: cvs tag r21-5-x
SY> Then: cvs tag -F r21-5-latest-beta
SY> All the magic is in the '-F'. It 'F'orces files to be tagged
with
SY> this tag even if a previous version of the file already has a tag of
SY> the same name.[2]
SY> Because it is "sticky" if you do a 'cvs up' in a working
directory that
SY> was checked out with 'cvs co -r r21-5-latest-beta xemacs', nothing
will
SY> get updated in your working directory until I move the tag ('cvs tag
SY> -F...') to the next release.
SY> Is that nifty or what? :-)
Yep.
So r21-5-latest-beta is basically an alias for the latest tagged beta
release, right?
APA> and where does it point to (latest sources or latest
APA> beta release sources)?
SY> Latest beta release sources. In other words, the contents of
SY> 'xemacs-21.5.10.tar.gz' on ftp.xemacs.org is more or less identical to
SY> what the current r21-5-latest-beta tag points to in CVS.
Why "more or less"? What's the variance between the two? Is it other
people commiting between your tagging operations?
SY> Does that clear it up for you, Adrian? If not, just yell.
Yep, thanks!
Would be nice to have explanations of our tagging name conventions on
the website, perhaps reachable via http://www.xemacs.org/Develop/
Adrian
SY> Footnotes:
SY> [1] For those who are worried, I don't make the decision that way,
SY> normally I wait until the 10th coffee. :-)
SY> [2] Files in CVS can only have unique tag names.
SY> --
SY> |---<Steve Youngs>---------------<GnuPG KeyID: 10D5C9C5>---|
SY> | XEmacs - It's not just an editor. |
SY> | It's a way of life. |
SY> |------------------------------------<youngs(a)xemacs.org>---|
--
Adrian Aichner
mailto:adrian＠xemacs.org
http://www.xemacs.org/
12:52 a.m.
|--==> "APA" == Adrian Aichner <adrian(a)xemacs.org> writes:
>>>>>"SY" == Steve Youngs
<youngs(a)xemacs.org> writes:
SY> By yours truly. :-) Usually after my 6th
or 7th coffee for the day I
SY> might say "lets release a beta, just for kicks..."[1]. After I've
APA> Oh, in that case you need to put your coffee statistics up under
APA> http://www.xemacs.org/coffee/ so that the beta community can track the
APA> tagging progress.
Sure, just as soon as I patch coffee.el to automatically update the
stats for me. :-)
SY> Is that nifty or what? :-)
APA> Yep.
APA> So r21-5-latest-beta is basically an alias for the latest tagged beta
APA> release, right?
I suppose that you could put it that way, yes.
SY> Latest beta release sources. In other words, the contents of
SY> 'xemacs-21.5.10.tar.gz' on ftp.xemacs.org is more or less identical to
SY> what the current r21-5-latest-beta tag points to in CVS.
APA> Why "more or less"? What's the variance between the two? Is it
other
APA> people commiting between your tagging operations?
No, it's nothing like that. The differences are that the tarball
doesn't have any 'CVS' directories or '.cvsignore' files[1], and
there
are no '.info' files in CVS whereas they exist in the tarball.
To put your mind at rest, if someone was to commit between my tagging
operations I wouldn't be affected (unless I 'cvs up' in between the 2
tags). CVS tags the repository from the versions of the files in my
workspace, it doesn't matter if newer versions of the files exist in
the repository.
APA> Would be nice to have explanations of our tagging name conventions on
APA> the website, perhaps reachable via http://www.xemacs.org/Develop/
http://www.xemacs.org/Develop/cvsaccess.html#tags
Footnotes:
[1] I also clean out any .orig and .rej files that may be in my
workspace.
--
|---<Steve Youngs>---------------<GnuPG KeyID: 10D5C9C5>---|
| XEmacs - It's not just an editor. |
| It's a way of life. |
|------------------------------------<youngs(a)xemacs.org>---|
7989
days inactive
7990
days old
4 comments
2 participants
participants (2)
-
Adrian Aichner -
Steve Youngs