From: Eli Zaretskii <eliz@gnu.org>
To: John Wiegley <jwiegley@gmail.com>
Cc: rgm@gnu.org, eggert@cs.ucla.edu, deng@randomsample.de,
lekktu@gmail.com, emacs-devel@gnu.org, schwab@suse.de
Subject: Re: Future release schedules (was: make change-history on non-master branches)
Date: Fri, 20 Nov 2015 20:04:17 +0200 [thread overview]
Message-ID: <83h9kg5yzi.fsf@gnu.org> (raw)
In-Reply-To: <m27flc1v90.fsf_-_@newartisans.com>
> From: John Wiegley <jwiegley@gmail.com>
> Cc: Juanma Barranquero <lekktu@gmail.com>, schwab@suse.de, eggert@cs.ucla.edu, rgm@gnu.org, deng@randomsample.de, emacs-devel@gnu.org
> Date: Fri, 20 Nov 2015 08:38:35 -0800
>
> >>>>> Eli Zaretskii <eliz@gnu.org> writes:
>
> > Alas, it's not just the pretest, it's the entire life time of the release
> > branch. That life time is just starting for the emacs-25 branch; I'm quite
> > certain that at lease Emacs 25.2 and probably also 25.3 will be delivered
> > from that branch. That's another 2 years. I don't think we want to wait that
> > long for your useful corrections and general loving care of ChangeLog.2 ;-)
> >
> > I hope we will find a better solution to this.
>
> Once 25.1 is out -- and this could take up to six months -- I'd like us to
> switch to a different process for point releases: A new .x release every two
> months, with whatever bug fixes have been accomplished in that interim.
>
> Once the emacs-25 branch is stable, say at 25.2, primary development would
> resume on master towards emacs-26. However, bugs will continue to be fixed and
> back-ported to emacs-25, with regular point releases from that branch, until
> it's stable enough to no longer need our attention. Beyond that point, it
> becomes a frozen branch -- unless a critical bug fix occurs justifying a point
> release solely for that fix.
That's what we did with emacs-24 branch as well. So this is not a new
process, it's a continuation of the process we've been practicing for
several years.
> The intention here is to maximize the utility of Git, now that we have it, and
> to make use of its branching, merging and cherry-picking capabilities to
> accelerate development, without sacrificing attention to stability for the
> current "release series". I like that we have gitmerge.el, for example; I hope
> we can adapt our release process to take full advantage of it.
We had all that before, with Bazaar as well.
next prev parent reply other threads:[~2015-11-20 18:04 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-15 2:15 make change-history on non-master branches Glenn Morris
2015-11-15 7:11 ` Paul Eggert
2015-11-16 16:02 ` Eli Zaretskii
2015-11-18 18:10 ` Glenn Morris
2015-11-18 18:19 ` Eli Zaretskii
2015-11-18 18:28 ` Glenn Morris
2015-11-18 18:46 ` Eli Zaretskii
2015-11-18 19:36 ` David Kastrup
2015-11-19 8:35 ` Andreas Schwab
2015-11-19 15:49 ` Eli Zaretskii
2015-11-19 16:35 ` Andreas Schwab
2015-11-19 17:02 ` Eli Zaretskii
2015-11-19 19:48 ` David Engster
2015-11-19 20:38 ` Eli Zaretskii
2015-11-19 20:57 ` David Engster
2015-11-20 0:31 ` Juanma Barranquero
2015-11-20 8:09 ` Eli Zaretskii
2015-11-20 16:38 ` Future release schedules (was: make change-history on non-master branches) John Wiegley
2015-11-20 18:04 ` Eli Zaretskii [this message]
2015-11-20 18:15 ` Future release schedules John Wiegley
2015-11-20 18:41 ` Future release schedules (was: make change-history on non-master branches) Artur Malabarba
2015-11-20 18:43 ` Artur Malabarba
2015-11-20 18:49 ` Eli Zaretskii
2015-11-20 19:05 ` Eli Zaretskii
2015-11-20 19:14 ` Future release schedules John Wiegley
2015-11-20 21:16 ` Eli Zaretskii
2015-11-20 21:33 ` John Wiegley
2015-11-21 11:14 ` Eli Zaretskii
2015-11-18 19:22 ` make change-history on non-master branches Eli Zaretskii
2015-11-18 20:38 ` Glenn Morris
2015-12-20 18:53 ` Glenn Morris
2015-12-20 21:21 ` Paul Eggert
2015-12-21 0:30 ` Glenn Morris
2015-12-23 1:12 ` John Wiegley
2015-12-23 7:58 ` Paul Eggert
2016-01-25 16:55 ` Glenn Morris
2016-01-25 17:22 ` Eli Zaretskii
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=83h9kg5yzi.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=deng@randomsample.de \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=jwiegley@gmail.com \
--cc=lekktu@gmail.com \
--cc=rgm@gnu.org \
--cc=schwab@suse.de \
/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.