[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Future release schedules
From: |
John Wiegley |
Subject: |
Re: Future release schedules |
Date: |
Fri, 20 Nov 2015 11:14:46 -0800 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.5 (darwin) |
>>>>> Eli Zaretskii <address@hidden> 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
- Re: make change-history on non-master branches, (continued)
- Re: make change-history on non-master branches, David Engster, 2015/11/19
- Re: make change-history on non-master branches, Juanma Barranquero, 2015/11/19
- Re: make change-history on non-master branches, Eli Zaretskii, 2015/11/20
- Future release schedules (was: make change-history on non-master branches), John Wiegley, 2015/11/20
- Re: Future release schedules (was: make change-history on non-master branches), Eli Zaretskii, 2015/11/20
- Re: Future release schedules, John Wiegley, 2015/11/20
- Re: Future release schedules (was: make change-history on non-master branches), Artur Malabarba, 2015/11/20
- Re: Future release schedules (was: make change-history on non-master branches), Artur Malabarba, 2015/11/20
- Re: Future release schedules (was: make change-history on non-master branches), Eli Zaretskii, 2015/11/20
- Re: Future release schedules (was: make change-history on non-master branches), Eli Zaretskii, 2015/11/20
- Re: Future release schedules,
John Wiegley <=
- Re: Future release schedules, Eli Zaretskii, 2015/11/20
- Re: Future release schedules, John Wiegley, 2015/11/20
- Re: Future release schedules, Eli Zaretskii, 2015/11/21
- Re: make change-history on non-master branches, Eli Zaretskii, 2015/11/18
- Re: make change-history on non-master branches, Glenn Morris, 2015/11/18