Re: Your latest commits on emacs-25

[Eli Zaretskii <eliz@gnu.org>]

> Date: Tue, 19 Apr 2016 21:28:45 -0400
> From: Mark Oteiza <mvoteiza@udel.edu>
> Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
> 
> AIUI emacs-25 is fine for safe changes; these are small fixes which had
> patches on the list for some time (with the exception of aa0d83a, though
> it is the same kind of fix as the other in rect.el).  If this is not the
> case, please advise.
> 
> There has been much churn over what the purpose of the branches are, the
> rationale of which was neither explained nor clarified on the relevant
> thread on which I specifically recall mentioning what the status quo was
> and asking why it was being changed.

AFAIU, the policy about the emacs-25 branch was stated by John here:

  http://lists.gnu.org/archive/html/emacs-devel/2016-03/msg00648.html

It reads:

  I'd like to begin the period of final stabilization toward a 25.1 release
  before the summer (which would officially mean June 21st).

  This means that starting now-ish, the only commits that should appear against
  emacs-25 are those that address a serious problem, or are obviously safe and
  an improvement over something we don't want to appear in the release (typos,
  missing an option from a list of alternatives, etc).

  When in doubt about the relevance of a change, please ask here. Otherwise,
  changes outside this scope, but still intended for 25.x, should be queued in
  master toward 25.2, with some indication that it is to be cherry-picked into
  emacs-25 once the release has been cut.

HTH