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: Thu, 11 Feb 2016 11:33:44 -0800 Message-ID: <56BCE218.8080703@dancol.org> 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> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="iRXkT2Shs5abCMTb9FdJk3sga53cSqOqb" X-Trace: ger.gmane.org 1455219253 28973 80.91.229.3 (11 Feb 2016 19:34:13 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 11 Feb 2016 19:34:13 +0000 (UTC) To: =?UTF-8?Q?=c3=93scar_Fuentes?= , emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Feb 11 20:34:12 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 1aTx0G-00021F-22 for ged-emacs-devel@m.gmane.org; Thu, 11 Feb 2016 20:34:12 +0100 Original-Received: from localhost ([::1]:52999 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aTx0C-00086H-3p for ged-emacs-devel@m.gmane.org; Thu, 11 Feb 2016 14:34:08 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:49465) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aTwzx-000868-VP for emacs-devel@gnu.org; Thu, 11 Feb 2016 14:33:54 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aTwzx-0000s4-3M for emacs-devel@gnu.org; Thu, 11 Feb 2016 14:33:53 -0500 Original-Received: from dancol.org ([2600:3c01::f03c:91ff:fedf:adf3]:56062) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aTwzw-0000rv-Os for emacs-devel@gnu.org; Thu, 11 Feb 2016 14:33:53 -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=dgznCj55X4QWWROd40JfbUljWSFmyjnWT1+h8yJdH0M=; b=cluCmoob92yP1wkxUWiEzdCsne3jeBBFt+Z6bVuCnSKyR3rIBmTiroAgWdvNpQGMqdKfH/+bHCvB1RHutAoRJuP3+O/S/t4zXMcC/CRN7yvR+fl1QPp+W1kS6t7bW9V0L2AMOhnG+TWCykWg81jrZjxsWwrjZpSKx7pMGWW+fO7CDQdmOOtjco1HAstygwGAyO236WqIbsUV/46kbSBJ93CMUgF7A/FxKRz5rNd+ZinQdOlwsfs272QWRw3VKlN2fL49HGvloog43a3EDQ2TXVc//bqLmT4h5SNhaogFHZMzK6KEk/6GcTRWV6rYNb5MRCqrejnhjGeqrpuiwK1EYA==; Original-Received: from [2620:10d:c090:180::2915] (helo=[IPv6:2620:10d:c081:1103:2ab2:bdff:fe1c:db58]) by dancol.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84) (envelope-from ) id 1aTwzu-00028K-Mc; Thu, 11 Feb 2016 11:33:50 -0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1 In-Reply-To: X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. 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:199768 Archived-At: This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --iRXkT2Shs5abCMTb9FdJk3sga53cSqOqb Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 02/11/2016 07:24 AM, John Wiegley wrote: > It appears that we have several possible scenarios available to us, and= each > has its trade-offs. >=20 > OPTION #3 >=20 > 25.1 is developed on emacs-25 > 26.1 is concurrently developed on master >=20 > This means dropping point releases, except for back-patching severe b= ug > fixes onto emacs-25. >=20 > DOWNSIDE: Package authors will experience API breakages more often, s= ince > every release of Emacs is now free to break them. There would be no p= olicy > of compatibility, as there is now (mostly) between point releases. FWIW, I'm not proposing anything as aggressive as breaking compatibility every release. It's easy enough to maintain API compatibility for a pre-set number of point releases, and this policy could replace point release compatibility. A deprecation period of six months to a year is a reasonable period for expecting external package developers to adapt to new APIs. --iRXkT2Shs5abCMTb9FdJk3sga53cSqOqb 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 iQIcBAEBCAAGBQJWvOIYAAoJEN4WImmbpWBl1ncP/RHV9iY+yTbEYQa15uqyE0qA 14FKhCDtwoL22ycjVZXNC6euJ/l8e7WdiKHN3RfB7AWdxmbGHPIp8WxPUR3pdkoS L5q5MaosgxmNHKFuqkq06TNE5HBOudYu1EwtAGp8FprO/eFvp3Mv1SkDVyrlINhi FHluMutscR40CKWmEZNcp2OV1mrT510/nVN/r231h79pPwxyXeXN2NvITMcdT6Ow vEIi0Kw9qJcigH+UEyuQEvYpWjcvYfyBCxd6GOloYvyQHNgPAd4EgpCsUwtsdRCT bSKx8Jdu290heWrqq4Za9sgH+nhc5ZVP7cGemuNwFCM+9VJiMCWYdUgT2SuKHiT9 ADwjnc8suOnMv1ALlcmRns+TnFPx/x9HXcHzNpAPUY30p8/jklsL95qy2Lp/Bq/M VjQjjOnjRYHpi9AT/Qex3ILRnnWtkUKjZEjob9CkjWLGLmc+D8kr2PfaBtWLW+Ch Lp/aOq8dJJVTWG1IJkLJDkv+6wVPuB4Z/bh06o5lnjhClA1+vySafPi5ZtExJ8zN 63AjaHv6V8IVvt+8snwyGERVIUbNOKB6h1t/d3b2FMFSNjCyrMNKNGhuoFV06+5Q AjsLNQy0RDRm5pZRiudNV7bj1g4bIGjawkXN/iSZsDaLtyDAf+j9KsnnxHX00g5P 9Jv8XjpiNJy71PCSPeWq =M8Do -----END PGP SIGNATURE----- --iRXkT2Shs5abCMTb9FdJk3sga53cSqOqb--