From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Daniel Colascione Newsgroups: gmane.emacs.devel Subject: Re: Next release from master Date: Mon, 18 Jan 2016 13:31:51 -0800 Message-ID: <569D59C7.8030602@dancol.org> References: <83a8o2evc0.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="P4AmTSGxkBe2t1rebOMEe4opngmvMSeoU" X-Trace: ger.gmane.org 1453152751 10102 80.91.229.3 (18 Jan 2016 21:32:31 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 18 Jan 2016 21:32:31 +0000 (UTC) To: Eli Zaretskii , monnier@iro.umontreal.ca, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jan 18 22:32:23 2016 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1aLHPT-0007q7-EB for ged-emacs-devel@m.gmane.org; Mon, 18 Jan 2016 22:32:23 +0100 Original-Received: from localhost ([::1]:33765 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aLHPS-0005ar-Qt for ged-emacs-devel@m.gmane.org; Mon, 18 Jan 2016 16:32:22 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:34830) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aLHP7-0005Xj-9v for emacs-devel@gnu.org; Mon, 18 Jan 2016 16:32:02 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aLHP6-0001jf-4X for emacs-devel@gnu.org; Mon, 18 Jan 2016 16:32:01 -0500 Original-Received: from dancol.org ([2600:3c01::f03c:91ff:fedf:adf3]:49560) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aLHP5-0001jM-Pn; Mon, 18 Jan 2016 16:32:00 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=dancol.org; s=x; h=Content-Type:In-Reply-To:MIME-Version:Date:Message-ID:From:References:To:Subject; bh=MEmb/M2icm6COM/6bJDorg6uiN/iL7fdbaRzFXZ+UDc=; b=dkFU7wNgudMWuWfUywClRpEjdxEdHbbiTMEGFks1km9my6FIWwQGET2ryGM9abr9dXdAYUUYV7Lpkw7YVIVha94+Z0Zk9ikVPgflPhgGuwqMqfI//7N30XYMInLoHIIUHKi6CnykcFO8pRgdAauPxSIv1lzP/4moSB13upQ13dp3wkosUCU2ik/jjGaZQf6DjietSLfDmnZN9SNj5ufmkOz8uXIfJizijDyXfXtIecWd8BvPEO3hFWXSNJ00FozexxcMAW76mDfWMDWH8BD5qoR6yT0fZF3J4SnO2y33yl2CUTWEmkcDJ8K0hNSlNAcD4oHiEWpHj1eRP5NUlBENhw==; Original-Received: from [2620:10d:c090:180::1:9578] (helo=[IPv6:2620:10d:c081:1110::106e]) by dancol.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84) (envelope-from ) id 1aLHP4-0003CK-1u; Mon, 18 Jan 2016 13:31:58 -0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 In-Reply-To: X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2600:3c01::f03c:91ff:fedf:adf3 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:198293 Archived-At: This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --P4AmTSGxkBe2t1rebOMEe4opngmvMSeoU Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 01/18/2016 01:13 PM, John Wiegley wrote: >>>>>> Eli Zaretskii writes: >=20 >>> master should become emacs-26 at some point in the future, once it's = ready, >>> while emacs-25 should only continue to improve and stabilize the 25.x= >>> series. >=20 >> Are you changing your mind? ;-) You told me something different in >> http://lists.gnu.org/archive/html/emacs-devel/2015-11/msg01372.html. >=20 > Yes, I suppose I am. >=20 > 'master' should be a place where people can commit API-breaking changes= once > they are ready for general consumption; otherwise, such changes would h= ave to > live in feature branches for a very long time, and we'd have little abi= lity to > test them in combination. >=20 > However, changes of that magnitude shouldn't happen between 25.1 and 25= =2E2; > that's not what a minor release means to me. When things really start > changing, we should think of them as going into the next major release.= >=20 > Therefore, the emacs-25 branch will stabilize over time until there's n= othing > more to do there. Although many will abandon the branch altogether in f= avor of > master at some point, there might still be some who wish to fix bugs th= ere and > call for a point release. >=20 > I imagine this will lead to more frequent major releases, and fewer poi= nt > releases, but that really depends on what we're doing. The more bug wor= k we > do, the more point releases; the more feature work, the more major rele= ases. >=20 > I'm not sure that I'm calling for anything radically different than wha= t has > happened before, though. Are you saying that in the past, what is now = master > would become 25.2? What then of features that are destined for 26 and n= ot > future versions of 25.x? >=20 >> You seem to be talking about something that never happened before in E= macs: >> we never left any branch "for maintenance", we left it for good. Once = the >> decision was made that the next release will be from master, the branc= h was >> abandoned, and never revisited except in emergency (e.g., if some >> super-critical bug was reported in the last release that required an u= rgent >> fix). >=20 > Yes, I may be talking about something that never happened before in Ema= cs, but > it's been valuable on other projects, so I thought we might try it here= as > well. >=20 > That said, if a shift to master means no one ever fixes another bug on > emacs-25, then there will be effectively no change; but the branch can = still > hang around for a while, and be available for point releases if necessa= ry. >=20 I'd be happy with switching to a less-like release scheme and incrementing a single number. Do minor releases even make sense anymore? --P4AmTSGxkBe2t1rebOMEe4opngmvMSeoU Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCAAGBQJWnVnHAAoJEN4WImmbpWBlF/cP/RV9s064FBToMZAxuUUJVBVv Om27wfSDqn0QPQ5fG9rPU3O5LZAi2pfVWlY7ArAfyqe2Dwq4vmOqHA7m1fSwjWuQ //TxaM96oLZybYJd+OKMkUq2B4uycHlvdSzNHRDew7QHjyg9UmdAQ+7ykkdcqQGU 8zHS5VAQhaT6ZYrfPY74USNpgB3/wCjwDQ54eCAKk4tIlAEMcQ9cWRMes/Yj4c+1 /pRaDPbZoNX1R4tXn2BMgBgpsd/HLa2MlKYgEbtpk1D7+T89klcyYhPppJn9qYtQ YE8rcrnyRno1jdVlZO9qQn+xr5aaNlzCEgh0FhPebqkQUrX6w2WPlLn8GIo4vx8J vrawUIMdz1Z/7s8OPrycB08bpOOXKSCpyx1B1PeQaSwlZisFrssF/86LtHQATUPA jLWLBfPr6yowCpf5T9YXjFffdrXHt3Cts8VmWHYAgH8ciCu2xohcQIB86Kz43Kk/ NNSTYK34DaOBcwkglJlxEeRF/2fgetIaGIJG7O8ilMMMqSiRGVUN8YnnxBgj3bdS iVfK9dJlIsZkGMw+qbExj2PYpZwMhacPP28htw1+R1Dh9EmGr0nGyfKX5oVOaKac spXDA8VUiiHQTms5+OUG7XnCMExuih9tdj1PZCHI2hHFi/p9+xCY3qoUwemTpx1D XANvWQWbLHD+Txrk40fV =ZNv4 -----END PGP SIGNATURE----- --P4AmTSGxkBe2t1rebOMEe4opngmvMSeoU--