From: Philip Kaludercic <philipk@posteo.net>
To: "Jostein Kjønigsen" <jostein@secure.kjonigsen.net>
Cc: Bozhidar Batsov <bozhidar@batsov.dev>,
Emacs Devel <emacs-devel@gnu.org>,
jostein@kjonigsen.net
Subject: Re: Allowing rolling release packages on ELPA
Date: Mon, 24 Oct 2022 16:00:31 +0000 [thread overview]
Message-ID: <87czah43fk.fsf@posteo.net> (raw)
In-Reply-To: <7c2bdbbd-bd23-cda9-50d4-23c4702215df@secure.kjonigsen.net> ("Jostein Kjønigsen"'s message of "Mon, 24 Oct 2022 08:45:35 +0200")
Jostein Kjønigsen <jostein@secure.kjonigsen.net> writes:
> On 24.10.2022 08:14, Bozhidar Batsov wrote:
>> The patch seems fine to me, but I'm a bit skeptical about the whole
>> rolling releases idea in general
>
> This is the default operation for MELPA, which arguably has more
> popular packages than ELPA.
To my knowledge all of the major packages on MELPA are also available
via GNU or NonGNU ELPA, so I don't know if this is really an argument.
>> How hard it is for people to actually update version timestamps
>> themselves or to just stick to the *-devel repos if they don't want
>> to cut releases?
>
> As a package-developer, I may release patches weekly, but I update
> main versions maybe once every second year, if/when someone bothers me
> about it.
>
> Not having to version things manually is a god-send.
It really depends, I am certainly no recommending to enable this by
default. The idea is just to accommodate people like you who prefer
this mode of publishing releases.
next prev parent reply other threads:[~2022-10-24 16:00 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 [this message]
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
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=87czah43fk.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=bozhidar@batsov.dev \
--cc=emacs-devel@gnu.org \
--cc=jostein@kjonigsen.net \
--cc=jostein@secure.kjonigsen.net \
/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.