Re: Version naming

[Thien-Thi Nguyen <ttn@gnu.org>]

[-- Attachment #1: Type: text/plain, Size: 1586 bytes --]

() Stefan Monnier <monnier@iro.umontreal.ca>
() Mon, 29 Sep 2014 13:19:08 -0400

   So I'll keep it short to get the discussion started:

      The next release from trunk will be called 25.1 rather than 24.5

Cool.

   There, I said it.  For completeness, here's the motivation: In
   retrospect 24.3 should have been named 25.1 and 24.4 should
   have been named 26.1.  The ".N" thingy should really be kept
   only for bug-fix releases and neither of 24.3, 24.4, nor the
   previously planned 24.5 are bug-fix releases.

You should write all this in admin/notes/versioning, or somesuch.
That way, the need (or rather, people's desire) for this...

   I'll stop listening to this thread starting right about now,
   but don't let that stop you wasting your time debating at
   length about this boring subject,

...can be much reduced.  A repo'd document also has the advantage
of providing an evolvable base for attaching labels (such as
"stable", "bugfix", etc), the most likely-to-succeed way out of
the next rat's nest (i.e., preferred/"official" Emacs-under-Git
branch discipline/manglement/workflow) discussion.  Just watch!

I say "you should" as a shorthand for "we should, and i (in my own
crass and clumsy way) will do so RSN if someone who has more
impact doesn't beat me to it".  (In this case, RSN == one week.)

-- 
Thien-Thi Nguyen
   GPG key: 4C807502
   (if you're human and you know it)
      read my lisp: (responsep (questions 'technical)
                               (not (via 'mailing-list)))
                     => nil

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]