From: Eli Zaretskii <eliz@gnu.org>
To: Mark Oteiza <mvoteiza@udel.edu>
Cc: jwiegley@gmail.com, emacs-devel@gnu.org
Subject: Re: Your latest commits on emacs-25
Date: Wed, 20 Apr 2016 17:40:33 +0300 [thread overview]
Message-ID: <83vb3c738e.fsf@gnu.org> (raw)
In-Reply-To: <20160420012845.GA4548@holos.localdomain> (message from Mark Oteiza on Tue, 19 Apr 2016 21:28:45 -0400)
> 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
prev parent reply other threads:[~2016-04-20 14:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-16 19:16 Your latest commits on emacs-25 Eli Zaretskii
2016-04-16 20:36 ` John Wiegley
2016-04-19 16:28 ` John Wiegley
2016-04-20 1:28 ` Mark Oteiza
2016-04-20 1:47 ` John Wiegley
2016-04-20 5:58 ` Paul Eggert
2016-04-20 14:40 ` Eli Zaretskii [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83vb3c738e.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jwiegley@gmail.com \
--cc=mvoteiza@udel.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.