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: use-package.el -> Emacs core Date: Tue, 10 Nov 2015 12:27:28 -0800 Message-ID: References: <864mgtaf6l.fsf@stephe-leake.org> <56424B8C.7060403@yandex.ru> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1447187576 6296 80.91.229.3 (10 Nov 2015 20:32:56 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 10 Nov 2015 20:32:56 +0000 (UTC) Cc: Emacs developers , Dmitry Gutov To: Kaushal Modi Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Nov 10 21:32:38 2015 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 1ZwFao-0007Lc-0G for ged-emacs-devel@m.gmane.org; Tue, 10 Nov 2015 21:32:38 +0100 Original-Received: from localhost ([::1]:35421 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZwFan-0002Y6-L5 for ged-emacs-devel@m.gmane.org; Tue, 10 Nov 2015 15:32:37 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:54392) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZwFai-0002Xb-Iu for emacs-devel@gnu.org; Tue, 10 Nov 2015 15:32:33 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZwFad-0008AP-TZ for emacs-devel@gnu.org; Tue, 10 Nov 2015 15:32:32 -0500 Original-Received: from mail-pa0-x232.google.com ([2607:f8b0:400e:c03::232]:35066) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZwFad-0008AF-Nr for emacs-devel@gnu.org; Tue, 10 Nov 2015 15:32:27 -0500 Original-Received: by pasz6 with SMTP id z6so7380604pas.2 for ; Tue, 10 Nov 2015 12:32:27 -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:mail-followup-to:mime-version:content-type; bh=CnMfGWbRQeBkR4cfH/xWt63nX3HNXZYqRkAxuZwFXVc=; b=yMX5vscK7BVSTa1D1e3m4g9Bl1z3rmddAtfEC/cyGTft3unlbU+v/mLGpcTuFqGYjk OoYQcqIsskZg6KzLsZB+GNlWrfJDDd0N4knUTC2gkQpu08XKHoIY6UXfbaCAw7bGAc2h HLj5e3VY2ZlOV2iBFdg8ymWrAUPstuhpBVeb0Xatzg4rlPudykr8JCowppY7yWzZ519T tRfk17BKk5R6Yt4P1ebowXvD2BodkF4Rt1kcNXCK+n3pXHz7OOp7cfEaC/qDcNvD04+7 gRxOxClJLvEGl+0I+BevohsWqo0yKIT3DaKBxkPcKpFONSe0rhpJZkLnx5n1iTcEUCoK 48Mw== X-Received: by 10.68.200.66 with SMTP id jq2mr8707075pbc.4.1447187547238; Tue, 10 Nov 2015 12:32:27 -0800 (PST) Original-Received: from Vulcan.attlocal.net (76-234-68-79.lightspeed.frokca.sbcglobal.net. [76.234.68.79]) by smtp.gmail.com with ESMTPSA id nu5sm5708833pbb.65.2015.11.10.12.32.25 (version=TLS1 cipher=AES128-SHA bits=128/128); Tue, 10 Nov 2015 12:32:25 -0800 (PST) X-Google-Original-From: "John Wiegley" Original-Received: by Vulcan.attlocal.net (Postfix, from userid 501) id 7513B1053F940; Tue, 10 Nov 2015 12:32:24 -0800 (PST) In-Reply-To: (Kaushal Modi's message of "Tue, 10 Nov 2015 15:09:29 -0500") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (darwin) Mail-Followup-To: Kaushal Modi , Dmitry Gutov , Emacs developers X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2607:f8b0:400e:c03::232 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:193962 Archived-At: >>>>> Kaushal Modi writes: > The development for use-package can continue as it is happening now and > versions can be git-tagged as something like "stable". When the time for > next emacs release comes, the GNU Elpa version can be synced with the latest > "stable" tagged version from the development git. Hmmm... you guys are both encouraging me to consider putting it in ELPA instead. It really kind of is an "optional package if you want to do things this way..." I so want that ELPA policy document now. :) We're spending too much time having this same debate about a fine line, like a hair in the dark. I think for 25.1, at least, everything I've suggested recently should go into ELPA. Then we'll let the policy document decide whether they belong in core for 25.2. John