From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: John Wiegley Newsgroups: gmane.emacs.devel Subject: Re: Next release from master Date: Thu, 11 Feb 2016 10:24:14 -0500 Message-ID: References: <8qegda3kfg.fsf@fencepost.gnu.org> <83h9i695n5.fsf@gnu.org> <87si118q6e.fsf@gnus.org> <877fid5u3e.fsf@gmx.us> <87bn7pwgaj.fsf@wanadoo.es> <87y4atqq25.fsf@gnus.org> <877fidwaka.fsf@wanadoo.es> <56BC0184.2040907@dancol.org> <87egcjuchi.fsf@wanadoo.es> Reply-To: John Wiegley NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" X-Trace: ger.gmane.org 1455204280 26107 80.91.229.3 (11 Feb 2016 15:24:40 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 11 Feb 2016 15:24:40 +0000 (UTC) Cc: emacs-devel@gnu.org To: =?utf-8?Q?=C3=93scar?= Fuentes Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Feb 11 16:24:33 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 1aTt6f-0002W0-BH for ged-emacs-devel@m.gmane.org; Thu, 11 Feb 2016 16:24:33 +0100 Original-Received: from localhost ([::1]:50959 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aTt6e-0007Qj-Kj for ged-emacs-devel@m.gmane.org; Thu, 11 Feb 2016 10:24:32 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:54007) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aTt6X-0007QV-7C for emacs-devel@gnu.org; Thu, 11 Feb 2016 10:24:30 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aTt6T-0006sn-UM for emacs-devel@gnu.org; Thu, 11 Feb 2016 10:24:25 -0500 Original-Received: from mail-yw0-x234.google.com ([2607:f8b0:4002:c05::234]:34286) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aTt6T-0006sX-Op for emacs-devel@gnu.org; Thu, 11 Feb 2016 10:24:21 -0500 Original-Received: by mail-yw0-x234.google.com with SMTP id h129so41493445ywb.1 for ; Thu, 11 Feb 2016 07:24:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:in-reply-to:date:message-id:references :user-agent:reply-to:mail-followup-to:mime-version:content-type; bh=xpYTU3j0/8Z1UU2jlw1AhNct7p2Anqqrt8ykL/xLRTo=; b=PXL3f8dqSZo0Qkaya5ExYLgO6Mwt7YrCrMRMaQSXPr40A7wr/pKsRYDL5vn0I7y88K 4/mhmOX1U4WNTd7d65zqumcM7tbb34q6n5CknhPpjSwzE3Lg7txtaHNGYV/39lmIAyxn UFQyyAmWxEkvDXOA0d6jHjw2J7T2NlfmtVgXNlGSV2n8e/H7UQuimNRK+n6KtBJLuRb9 wkiFRaLTPpY+euQ/1h6BpmlweydnJ44IMa3V9FP/4Mq117CqsVPRi+4WbJTvWIxEArCf xQ/dN4eNcDj7X/8OM7VI4Pcn0/JDkxW/U0bL/uTLL2+y0eCHuWMr1/9qKC3qaZVjU8ea 5ytQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:in-reply-to:date:message-id :references:user-agent:reply-to:mail-followup-to:mime-version :content-type; bh=xpYTU3j0/8Z1UU2jlw1AhNct7p2Anqqrt8ykL/xLRTo=; b=SjZMjUCu/xUp4aoqvZ7ZbNPnA24g8NlBUeSg3wUO7f55oRAXo47zhPt/MiOeYwpD/q GzprEje0+uHHr2jsyUVzgZcBK1AxRFu+KVTM5HJ41wdlgjC4+tMxq0fFAgbhmgsfNW0n FlWMMP7ycSDR++QKearoR3qm4r1b7KV2ior/CP4BU8YQkR0ZlL1tCIpI+NR1vXKts2l6 qQCkOVD/587b5RJw+4oKsAT9NewkLt2dwPK5kMph0eTHR5viQePQ1Lcwpmb3b9FSKYAG OpCpxeHRPXjCrpa1FHBgp12euZD8t9pGKzFV51HVQGMaJrdGsuTXQo5Rh5IPoqCjIgCb 7zWA== X-Gm-Message-State: AG10YORYLc4ztsUVy2SEX8vcdULSBaeTWPtqfR0mO3UhMg/6QTwmcKU4DEP1bN+Ho5BH3g== X-Received: by 10.129.159.208 with SMTP id w199mr13746700ywg.62.1455204261329; Thu, 11 Feb 2016 07:24:21 -0800 (PST) Original-Received: from Hermes.local (43.sub-70-192-8.myvzw.com. [70.192.8.43]) by smtp.gmail.com with ESMTPSA id t64sm6687201ywa.45.2016.02.11.07.24.19 (version=TLS1 cipher=AES128-SHA bits=128/128); Thu, 11 Feb 2016 07:24:19 -0800 (PST) X-Google-Original-From: "John Wiegley" Original-Received: by Hermes.local (Postfix, from userid 501) id 0298A4E102CA; Thu, 11 Feb 2016 10:24:18 -0500 (EST) In-Reply-To: <87egcjuchi.fsf@wanadoo.es> (=?utf-8?Q?=22=C3=93scar?= Fuentes"'s message of "Thu, 11 Feb 2016 04:55:53 +0100") User-Agent: Gnus/5.130014 (Ma Gnus v0.14) Emacs/24.5 (darwin) Mail-Followup-To: =?utf-8?Q?=C3=93scar?= Fuentes , emacs-devel@gnu.org X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2607:f8b0:4002:c05::234 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:199747 Archived-At: --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable It appears that we have several possible scenarios available to us, and each has its trade-offs. OPTION #1 (closest to the status quo) 25.1 is developed on emacs-25 25.2 is concurrently developed on master 26.1 is concurrently developed in other branches =20=20 LABOR: We need to move 26.1 commits out of master and into some other branch. Bugs that were marked "fixed in 25.2" that shouldn't have been, n= eed to be updated to say "fixed in 26.1". OPTION #2 25.1 is developed on emacs-25 25.2 is concurrently developed on emacs-25-next 26.1 is concurrently developed on master LABOR: Again, splitting the commits between master and emacs-25-next. Sa= me work as option #1. DOWNSIDE: 'master' potentially becomes much more unstable, and yet this is the default branch when people pull from Git. Solution: Change the defau= lt branch to emacs-XX-next. OPTION #3 25.1 is developed on emacs-25 26.1 is concurrently developed on master This means dropping point releases, except for back-patching severe bug fixes onto emacs-25. DOWNSIDE: Package authors will experience API breakages more often, since every release of Emacs is now free to break them. There would be no policy of compatibility, as there is now (mostly) between point releases. Unless you've managed a large Emacs project used by many, I'm not sure you fully understand what is implied by this decision. Someone suggested just cutting a new release arbitrarily every X months, but I don't feel that i= s a realistic option. OPTION #4 ??? Since the core developers are the ones doing the work, what works for them = is what we should do. If everyone wants API-breaky releases more often, we sho= uld consider that option. However, my preference is option #1, as it is the one that most emphasizes stability over "new features". =2D-=20 John Wiegley GPG fingerprint =3D 4710 CF98 AF9B 327B B80F http://newartisans.com 60E1 46C4 BD1A 7AC1 4BA2 --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQGcBAEBCgAGBQJWvKeeAAoJEMFE2PTxn+Yw0AYMAMUUlrHPJN8Q+317Nls+OL8m pBZTU26OuP431sfTqhCBcYU3WbQtbgGs2dR0qbM9QIPHjJ9K+n0mKY6Ax/mvhiCG jrwS+DDu23scHudCLQp5vw/SW9ky//wIN2tU42Ffr/KfZydnbMfvKEnT0TFQprxZ ztOB9eYvcyZY144dMLU8NxZtCuqrOHUyD6p/IKMcFXuRt4dtmvlt650fGIMlhid7 KQDVzcb9Zs6EOXZYidrj2sjGWEY/8B03OnqxSxq/l3O8qJ05DM9N/chrCBIoEugx 1/JHhI6P3AOiNGOkSCSElpG/IOmXCpp3hBpbKapenTud8o4ByQYFhg9cbyxIs4Uh 0MHGoFWUeBB5EQ7bShVDRbvX70x1hAflZnylmEL64oP2uamuj7GEdIlg6qU003Ws rTYJ8mS1LIu3l8Qm57jQhdI099ZeJnPzGTkslVVRQOQwDZtHvKyddbQcjLNLxFoP 3TTtb8zZ5mGEGTJgSHCw5NyRamJFETY3fxuXgzg/bg== =sgSs -----END PGP SIGNATURE----- --=-=-=--