[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: CONTRIBUTE and where to commit bug fixes
From: |
Karl Fogel |
Subject: |
Re: CONTRIBUTE and where to commit bug fixes |
Date: |
Mon, 24 Sep 2018 18:06:56 -0500 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) |
Stefan Monnier <address@hidden> 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