From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: "Bozhidar Batsov" Newsgroups: gmane.emacs.devel Subject: Re: Allowing rolling release packages on ELPA Date: Wed, 26 Oct 2022 08:10:25 +0300 Message-ID: <5340a07b-a9bb-41a1-add2-4c0fe3f66e8c@app.fastmail.com> References: <87o7u4p2t4.fsf@posteo.net> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=14a4aec1091044839137a83f6fa6c89e Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="16222"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Cyrus-JMAP/3.7.0-alpha0-1047-g9e4af4ada4-fm-20221005.001-g9e4af4ad To: "Emacs Devel" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Oct 26 07:13:17 2022 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1onYj4-00040D-J1 for ged-emacs-devel@m.gmane-mx.org; Wed, 26 Oct 2022 07:13:17 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1onYgp-0002dh-Rp; Wed, 26 Oct 2022 01:10:55 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1onYgm-0002Um-C8 for emacs-devel@gnu.org; Wed, 26 Oct 2022 01:10:52 -0400 Original-Received: from out1-smtp.messagingengine.com ([66.111.4.25]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1onYgk-0001G5-0G for emacs-devel@gnu.org; Wed, 26 Oct 2022 01:10:51 -0400 Original-Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 2AA645C00FC for ; Wed, 26 Oct 2022 01:10:47 -0400 (EDT) Original-Received: from imap43 ([10.202.2.93]) by compute5.internal (MEProxy); Wed, 26 Oct 2022 01:10:47 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=batsov.dev; h=cc :content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to; s=fm2; t=1666761047; x=1666847447; bh=tYQXggrf7f AhoSFaMkdVgr4wp4ka1z/+fuP+XUt18eI=; b=nOMx0Az3f+6KtNQ0BRjevl8+UP m+6Ezu1sl8v1OMFEGWqa1QotbVWTE0l3yZfScBjAygXWLZYhNH66kpGgxi9QS9UU uvIXmRDQWGnizfROzOSAt6NVL7m+PQsqybSwtU1O7zJVeJZR3/9skTvTwHJiK2Nb 0hmzCvPvA2d28OYVm60htdZexV4pwCvrjGV9ASQCt1CifPuPPL/+AcFlbsPqgLN7 mBxPfz+pwsLFOWpakCE0Zon/wR458fHCiWz6IE39mWTWXawxJA8eyIvHwQlXH1eU nqhqoAHZZ+oQkYGhKQEPKwgAKEJUmYFIkOab4YTOkcImD/Y42Z4LK5tSoO1A== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:date:feedback-id :feedback-id:from:from:in-reply-to:in-reply-to:message-id :mime-version:references:reply-to:sender:subject:subject:to:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm3; t=1666761047; x=1666847447; bh=tYQXggrf7fAhoSFaMkdVgr4wp4ka 1z/+fuP+XUt18eI=; b=FACEEHbSrizD17nRaVEnzlLZOD3ZlQDmBbz3xSnFsSmM hWQc7RKliexwga5fHcAW3Si20bkmcJLx+mYSDhppFfU8d+uGZvCswhPR8LkfqYNH VWYPIxQuN86pUqhP4yaUhJkbOyaEBm7qgh3EvIJ3UI5ZsiQ10RC6irMnvjYyy+bJ bJk5ouLJl8NAVbaXrGUus9ERU1YGEQCZCy8dX5sOrxkL55WfadLNgTmSzgWNjHEk lyt6GTO3IfB4wDBQnbaAsvBNHko3ccTOJtFracYSN2FSclPwHohmzfgPU+EjZHUa ovuE8lKMWJIf7VfSbCID9uXvQush7+gNhBNHdiWfRw== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvgedrtddugdelfecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefofgggkfgjfhffhffvufgtsegrtderreerredtnecuhfhrohhmpedfuehoiihh ihgurghruceurghtshhovhdfuceosghoiihhihgurghrsegsrghtshhovhdruggvvheqne cuggftrfgrthhtvghrnhepfefhffegieehleejieehudeghedvteeukefgudevueduhfef hfdtkeehjeelgeeunecuffhomhgrihhnpehmvghlphgrrdhorhhgpdhsthgrlhhlmhgrnh drohhrghdpghhnuhdrohhrghdpfhhsfhdrohhrghdpihhnthgvrhhnvghthhgrlhhlohhf fhgrmhgvrdhorhhgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilh hfrhhomhepsghoiihhihgurghrsegsrghtshhovhdruggvvh X-ME-Proxy: Feedback-ID: i025946a9:Fastmail Original-Received: by mailuser.nyi.internal (Postfix, from userid 501) id DB4D02D40071; Wed, 26 Oct 2022 01:10:46 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface In-Reply-To: Received-SPF: pass client-ip=66.111.4.25; envelope-from=bozhidar@batsov.dev; helo=out1-smtp.messagingengine.com X-Spam_score_int: -27 X-Spam_score: -2.8 X-Spam_bar: -- X-Spam_report: (-2.8 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: "Emacs-devel" Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:298511 Archived-At: --14a4aec1091044839137a83f6fa6c89e Content-Type: text/plain Instead of setting version numbers manually (e.g. 0.1, 0.2) upon release time, with rolling releases every change (commit) pushed upstream results automatically in a new release and a version bump, with the version being a timestamp. E.g. if I push 3 commits one day with some time between them this will result in 3 releases. I think it's a great approach for snapshot (devel) repos, but I'm not so sure about "stable" repos, as it kinda of implies that the author will never have their project in an inconsistent state (e.g. halfway towards a new feature). This approach was made popular by https://melpa.org/ On Tue, Oct 25, 2022, at 11:14 PM, Richard Stallman wrote: > [[[ To any NSA and FBI agents reading my email: please consider ]]] > [[[ whether defending the US Constitution against all enemies, ]]] > [[[ foreign or domestic, requires you to follow Snowden's example. ]]] > > > I have heard from people who prefer a rolling release model for their > > packages, > > Can you explain what that means, concretely? How is t different from > what we do now? > > and requested that their packages not be added for {Non,}GNU > > ELPA if they would have to update the version header manually, > > presumably on every commit. > > Is this something we would _want_ to do? What would its implications > be for Emacs? > > We might decide to support their style of release, or decide not to > include their packages in NonGNU ELPA, or we might come up with > another solution. I don't know what's best. But I'm sure we should > think about that before we decide. > > > -- > Dr Richard Stallman (https://stallman.org) > Chief GNUisance of the GNU Project (https://gnu.org) > Founder, Free Software Foundation (https://fsf.org) > Internet Hall-of-Famer (https://internethalloffame.org) > > > > --14a4aec1091044839137a83f6fa6c89e Content-Type: text/html Content-Transfer-Encoding: quoted-printable
Instead of sett= ing version numbers manually (e.g. 0.1, 0.2) upon release time, with rol= ling releases every change (commit) pushed upstream results automaticall= y in a new release and a version bump, with the version being a timestam= p.  E.g. if I push 3 commits one day with some time between them th= is will result in 3 releases. I think it's a great approach for snapshot= (devel) repos, but I'm not so sure about "stable" repos, as it kinda of= implies that the author will never have their project in an inconsisten= t state (e.g. halfway towards a new feature).

<= div>This approach was made popular by htt= ps://melpa.org/

On Tue, Oct 25, 2022, = at 11:14 PM, Richard Stallman wrote:
[[[ To any NSA and FBI agents reading my email= : please consider    ]]]
[[[ whether defend= ing the US Constitution against all enemies,     ]]]=
[[[ foreign or domestic, requires you to follow Snowden's= example. ]]]

  > I have heard from= people who prefer a rolling release model for their
 = ; > packages,

Can you explain what that = means, concretely?  How is t different from
what we d= o now?

      =         and requested that their pack= ages not be added for {Non,}GNU
  > ELPA if they w= ould have to update the version header manually,
  &g= t; presumably on every commit.

Is this some= thing we would _want_ to do?  What would its implications
=
be for Emacs?

We might decide to suppo= rt their style of release, or decide not to
include their = packages in NonGNU ELPA, or we might come up with
another = solution.  I don't know what's best.  But I'm sure we should
think about that before we decide.

=

-- 
Dr Richard Stallman (https://stallman.org)
Chief GNU= isance of the GNU Project (https://gnu.org)
Internet Hall-of-Famer (https://internethalloffame.org)




=

--14a4aec1091044839137a83f6fa6c89e--