From mboxrd@z Thu Jan  1 00:00:00 1970
Path: news.gmane.org!.POSTED!not-for-mail
From: Roland Winkler <winkler@gnu.org>
Newsgroups: gmane.emacs.devel
Subject: Re: RFC: Adding BBDB to Emacs core
Date: Tue, 17 Apr 2018 10:13:56 -0500
Message-ID: <877ep5euh7.fsf@gnu.org>
References: <m3zi265o49.fsf@fitzsim.org> <ygfvacuugb7.fsf@fastmail.com>
	<87lgdpphmm.fsf@ericabrahamsen.net> <ygfo9il1k4i.fsf@fastmail.com>
	<CAM9Zgm0yQjL+tOg1cRfyfshb4oQGFMJNJ5057K58S1Fj+bJsgw@mail.gmail.com>
	<m21sffn2tl.fsf@newartisans.com> <87vacqcy89.fsf@gnu.org>
	<jwvr2nef0fx.fsf-monnier+gmane.emacs.devel@gnu.org>
NNTP-Posting-Host: blaine.gmane.org
Mime-Version: 1.0
Content-Type: text/plain
X-Trace: blaine.gmane.org 1523977952 12307 195.159.176.226 (17 Apr 2018 15:12:32 GMT)
X-Complaints-To: usenet@blaine.gmane.org
NNTP-Posting-Date: Tue, 17 Apr 2018 15:12:32 +0000 (UTC)
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.2 (gnu/linux)
Cc: emacs-devel@gnu.org
To: Stefan Monnier <monnier@iro.umontreal.ca>
Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Apr 17 17:12:27 2018
Return-path: <emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org>
Envelope-to: ged-emacs-devel@m.gmane.org
Original-Received: from lists.gnu.org ([208.118.235.17])
	by blaine.gmane.org with esmtp (Exim 4.84_2)
	(envelope-from <emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org>)
	id 1f8SHT-000362-Ca
	for ged-emacs-devel@m.gmane.org; Tue, 17 Apr 2018 17:12:27 +0200
Original-Received: from localhost ([::1]:44538 helo=lists.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org>)
	id 1f8SJZ-0007W4-WA
	for ged-emacs-devel@m.gmane.org; Tue, 17 Apr 2018 11:14:38 -0400
Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:41168)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <winkler@gnu.org>) id 1f8SIy-0007VD-W1
	for emacs-devel@gnu.org; Tue, 17 Apr 2018 11:14:01 -0400
Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <winkler@gnu.org>) id 1f8SIv-0005p1-SC
	for emacs-devel@gnu.org; Tue, 17 Apr 2018 11:14:00 -0400
Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:45920)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <winkler@gnu.org>)
	id 1f8SIv-0005ov-OK; Tue, 17 Apr 2018 11:13:57 -0400
Original-Received: from lukas.physics.niu.edu ([131.156.224.124]:46602 helo=lukas)
	by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128)
	(Exim 4.82) (envelope-from <winkler@gnu.org>)
	id 1f8SIv-0003nG-Dh; Tue, 17 Apr 2018 11:13:57 -0400
In-Reply-To: <jwvr2nef0fx.fsf-monnier+gmane.emacs.devel@gnu.org> (Stefan
	Monnier's message of "Tue, 17 Apr 2018 09:07:46 -0400")
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic]
X-Received-From: 2001:4830:134:3::e
X-BeenThere: emacs-devel@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: "Emacs development discussions." <emacs-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-devel>,
	<mailto:emacs-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-devel/>
List-Post: <mailto:emacs-devel@gnu.org>
List-Help: <mailto:emacs-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-devel>,
	<mailto:emacs-devel-request@gnu.org?subject=subscribe>
Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org
Original-Sender: "Emacs-devel" <emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org>
Xref: news.gmane.org gmane.emacs.devel:224704
Archived-At: <http://permalink.gmane.org/gmane.emacs.devel/224704>

On Tue, Apr 17 2018, Stefan Monnier wrote:
> FWIW, currently GNU ELPA supports this in the following way: a new GNU
> ELPA package is only created once the "Version:" of a package is
> bumped.  So you can add experimental code to elpa.git's master branch
> without worrying about its effect on the distributed package and when
> that code is ready you can just bump the "Version:" header to cause a
> new release.

It would be nice to be able to go beyond that.  I am grateful if
adventurous users are willing to test the experimental code.  So it
would be nice if there was infrastructure that somehow allowed these
users to subscribe to the experimental code, similar to how the
development of core emacs benefits from users using the master branch.