all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: John Wiegley <jwiegley@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: rgm@gnu.org, eggert@cs.ucla.edu, deng@randomsample.de,
	lekktu@gmail.com, bruce.connor.am@gmail.com, emacs-devel@gnu.org,
	schwab@suse.de
Subject: Re: Future release schedules
Date: Fri, 20 Nov 2015 11:14:46 -0800	[thread overview]
Message-ID: <m21tbkwkih.fsf@newartisans.com> (raw)
In-Reply-To: <83bnao5w4s.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 20 Nov 2015 21:05:55 +0200")

>>>>> Eli Zaretskii <eliz@gnu.org> writes:

> IOW, I think we can only switch to this model if we drastically reduce the
> time interval between major releases, to something like a year or less, or
> if we start maintaining 3 branches, not 2. Both alternatives require radical
> changes in the process and the procedures, to say nothing about the
> manpower.

I'd like to cut new major releases once a year, even if they only introduce a
few new features. That is, there should always be two active branches: the
current release branch, and 'master' leading up to the next release branch.

There could also be a third branch, the previous release (i.e., emacs-24 right
now), if we really want to nail stability for people still on that version,
but I expect involvement on such a branch to remain low.

I'm not sure this requires a radical change in process and procedure. We keep
doing what we're doing today, we just release with shorter NEWS entries.

John



  reply	other threads:[~2015-11-20 19:14 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
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                                 ` John Wiegley [this message]
2015-11-20 21:16                                   ` Future release schedules 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=m21tbkwkih.fsf@newartisans.com \
    --to=jwiegley@gmail.com \
    --cc=bruce.connor.am@gmail.com \
    --cc=deng@randomsample.de \
    --cc=eggert@cs.ucla.edu \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --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.