[EMAIL PROTECTED] (Kim F. Storm) writes:
> Miles Bader <[EMAIL PROTECTED]> writes:
>
>> On Wed, 09 Feb 2005 01:17:30 +0100, Kim F. Storm <[EMAIL PROTECTED]> wrote:
>>> > On Tue, 08 Feb 2005 22:18:41 +0100, Jérôme Marant <[EMAIL PROTECTED]>
>>> > wrote:
>>> >> What's the rational for not using 22.0.x for development versions?
>>> >> It would be so much simpler ...
>>>
>>> Because it - IMO - is confusing.
>>
>> What, compared to all the other bizarro schemes being suggested here
>> ("hey I know, let's make pre-releases _blue_, and real releases
>> _green_!")? You've got to be kidding... please say you're kidding...
>
> Not really!
>
> The problem with our _current_ scheme is that even though we seem to
> want to postpone the decision about exactly what number the next
> release gets, it is recorded _NUMEROUS_ places all over the sources
> and other files (in total, I had to change 21.4 to 22.1 in more than
> 500 places).
That is not counting the 8000+ web pages containing Emacs-21.4...
> I don't want us to get into that mess again -- so I want a scheme
> where the next release number is _fixed_ from the start.
This assumes that most version numbers in the text can stay ("will be
available with version xxx" is a good candidate). That will still
need to cater for "the current version is xxx", but maybe _those_ can
partly be autogenerated with CVS keywords, depending on the kind of
text? In AUCTeX, we have something like
(eval-and-compile
(defconst AUCTeX-version
(eval-when-compile
(let ((name "$Name: $")
(rev "$Revision: 5.482 $"))
(or (when (string-match "\\`[$]Name: *\\(release_\\)?\\([^ ]+\\)
*[$]\\'"
name)
(setq name (match-string 2 name))
(while (string-match "_" name)
(setq name (replace-match "." t t name)))
name)
(if (string-match "\\`[$]Revision: *\\([^ ]+\\) *[$]\\'" rev)
(format "CVS-%s" (match-string 1 rev)))
"unknown")))
"AUCTeX version.
If not a regular release, CVS revision of `tex.el'."))
It's less than perfect, but at least it is something one can't
forget. It also means that you need to export using the version tag
when doing a release.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
