From: Karl Fogel <kfogel@red-bean.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: CONTRIBUTE and where to commit bug fixes
Date: Mon, 24 Sep 2018 18:06:56 -0500 [thread overview]
Message-ID: <87wora7awf.fsf@red-bean.com> (raw)
In-Reply-To: <jwv8t3r6o6z.fsf-monnier+gmane.emacs.devel@gnu.org> (Stefan Monnier's message of "Mon, 24 Sep 2018 09:14:03 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>Follow the list with enough dedication to know when we're in deep freeze
>and when we're not.
:-) Yeah -- I follow the list with light-to-medium dedication, and I usually can't tell whether we're in deep freeze.
(I realize your point above was sarcastic; I'm just agreeing with the sarcasm.)
>Maybe rather than document the way we work in more detail (which won't
>really help solve the problem, obviously), we could change the way we
>work to make it more clear:
>
>- when we start the "new major release" process, we create a new branch
> (e.g. emacs-27). Nothing new here.
>- when we enter the "deep freeze" process, rather than announce it and
> hope people will know about it, we create yet another branch
> (e.g. emacs-27.1).
>
>Then the rule can be documented more simply in the doc:
>- master is for new features.
>- emacs-NN is for any bug and doc fix.
>- emacs-NN.MM only takes bug fixes for regressions and requires explicit
> agreement from the maintainers.
>
>This also solves the problem of where to install non-regression bug
>fixes when we're in deep freeze.
+1 -- nice solution all around.
Best regards,
-Karl
next prev parent reply other threads:[~2018-09-24 23:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-07 0:56 CONTRIBUTE and where to commit bug fixes Michael Heerdegen
2018-09-24 12:53 ` Michael Heerdegen
2018-09-24 13:14 ` Stefan Monnier
2018-09-24 23:06 ` Karl Fogel [this message]
2018-09-25 2:49 ` Van L
2018-10-04 15:57 ` Michael Heerdegen
2018-10-04 16:35 ` John Wiegley
2018-10-04 16:38 ` Noam Postavsky
2018-10-04 20:43 ` Michael Heerdegen
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=87wora7awf.fsf@red-bean.com \
--to=kfogel@red-bean.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.