[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Next release from master
From: |
Eli Zaretskii |
Subject: |
Re: Next release from master |
Date: |
Fri, 22 Jan 2016 09:11:58 +0200 |
> From: John Wiegley <address@hidden>
> Date: Thu, 21 Jan 2016 17:01:50 -0800
>
> I think that maybe we need three branches: one for current release work (such
> as emacs-25); one towards the next release (master); and one towards the next
> major release (possible name: "next"?).
IMO, we shouldn't start another branch before we successfully pass the
exam for "branches 101" -- being able to reliably handle 2 branches.
Right now, we are not there yet, witness the latest merge problems.
And if this is just to solve the problem of references to the future
release in defcustom and in make-obsolete calls, then we should be
better off introducing some script that would change all of them
automatically when we change our decisions about where should the next
release come from.
- Re: Next release from master, (continued)
- Re: Next release from master, Stefan Monnier, 2016/01/23
- Re: Next release from master, Eli Zaretskii, 2016/01/22
- Re: Next release from master, Michael Albinus, 2016/01/22
- Re: Next release from master, Eli Zaretskii, 2016/01/22
- Re: Next release from master, Nicolas Petton, 2016/01/22
- Re: Next release from master, Michael Albinus, 2016/01/22
- Re: Next release from master, John Wiegley, 2016/01/22
- Re: Next release from master, Michael Albinus, 2016/01/22
- Re: Next release from master, Alan Mackenzie, 2016/01/22
- Re: Next release from master, Eli Zaretskii, 2016/01/22
- Re: Next release from master,
Eli Zaretskii <=
- Re: Next release from master, Stefan Monnier, 2016/01/23