Re: Next release from master

[Eli Zaretskii <eliz@gnu.org>]

> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Date: Sun, 17 Jan 2016 18:04:17 -0500
> 
> I noticed that etc/NEWS on master is setup for "25.2" being the next
> release from master.  Is that indeed the intention?

I think we don't know yet.

> My own conclusion based on how things worked during Emacs-24.N was that
> we're better off incrementing the major version every time there are new
> features.  IOW the next release form master should be called 26.1 and
> 25.N should be kept for a bugfix-only releases from the emacs-25 branch.

There's a new kid on the block (not me, I'm anything but "new" ;-),
and he needs time to make up his mind about what exactly will be
released, when, and how.  What you see now was asked and answered:

  From http://lists.gnu.org/archive/html/emacs-devel/2015-11/msg01372.html:

  > >>>>> Eli Zaretskii writes:
  > 
  > > We should now change master to identify itself as version 25.1.50 or maybe
  > > even 26.0.50. OK?
  > 
  > Let's go with 25.1.50 for now.

> It's not tremendously important, but the way we've done it in the past
> ended up with all kinds of minor inconveniences when we suddenly decide
> that we need another bugfix release: e.g. having to update all
> "make-obsolete" calls, not to mention all the "will be fixed in (or
> added to) Emacs-NN.MM" already posted in debbugs, mailing-lists,
> stackoverflow, forums, and newsgroups which suddenly become lies.

I don't see any good way around these issues, as long as the decisions
are dynamic and not subject to some fixed deterministic algorithm.
Even if we somehow force ourselves to make the decision now, there
will be similar issues in the other direction, see Michael's email
down-thread.

These issues are not a catastrophe, making those changes (where
necessary) is a simple (though boring and ungrateful) job.