From: Philip Kaludercic <philipk@posteo.net>
To: "Bozhidar Batsov" <bozhidar@batsov.dev>
Cc: "Emacs Devel" <emacs-devel@gnu.org>
Subject: Re: Allowing rolling release packages on ELPA
Date: Wed, 26 Oct 2022 06:30:41 +0000 [thread overview]
Message-ID: <87wn8nrt9q.fsf@posteo.net> (raw)
In-Reply-To: <5340a07b-a9bb-41a1-add2-4c0fe3f66e8c@app.fastmail.com> (Bozhidar Batsov's message of "Wed, 26 Oct 2022 08:10:25 +0300")
"Bozhidar Batsov" <bozhidar@batsov.dev> writes:
> 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.
Not quite, the time stamp is appended to the regular version number.
> 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).
Right, so it would only be used whenever a package author prefers that
method of development.
> 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?
It is currently necessary to bump the version tag in the package header
to indicate that a release is to be made. If a package specification
has a non-nil :rolling-release tag, then this is done whenever the
repository is synchronised.
>> 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?
It wouldn't affect Emacs, just packages that request this kind of
release management.
>> 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.
If the only issue a package has is that it is developed using a "rolling
release" model, it would be nonsensical for us to not accommodate the
request and reject a (perhaps popular) package on that ground.
next prev parent reply other threads:[~2022-10-26 6:30 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-22 10:31 Allowing rolling release packages on ELPA Philip Kaludercic
2022-10-23 4:47 ` Protesilaos Stavrou
2022-10-23 8:43 ` Philip Kaludercic
2022-10-24 6:14 ` Bozhidar Batsov
2022-10-24 6:45 ` Jostein Kjønigsen
2022-10-24 8:07 ` Bozhidar Batsov
2022-10-24 14:06 ` Stefan Kangas
2022-10-26 19:18 ` Richard Stallman
2022-10-24 16:00 ` Philip Kaludercic
2022-10-24 16:39 ` Jostein Kjønigsen
2022-10-26 19:18 ` Richard Stallman
2022-10-24 19:27 ` Stefan Monnier
2022-10-24 15:58 ` Philip Kaludercic
2022-10-24 17:27 ` Stephen Leake
2022-10-24 19:40 ` Stefan Monnier
2022-10-26 6:32 ` Philip Kaludercic
2022-10-26 11:57 ` Stefan Monnier
2022-10-26 15:27 ` Philip Kaludercic
2022-10-26 18:31 ` Philip Kaludercic
2022-10-26 18:55 ` Stefan Monnier
2022-10-26 19:07 ` Philip Kaludercic
2022-10-25 20:14 ` Richard Stallman
2022-10-26 5:10 ` Bozhidar Batsov
2022-10-26 6:30 ` Philip Kaludercic [this message]
2022-10-26 8:05 ` Bozhidar Batsov
2022-10-26 19:18 ` Richard Stallman
-- strict thread matches above, loose matches on Subject: below --
2022-10-26 5:58 Payas Relekar
2022-10-26 8:07 ` Bozhidar Batsov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wn8nrt9q.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=bozhidar@batsov.dev \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.