From: "Bozhidar Batsov" <bozhidar@batsov.dev>
To: "Emacs Devel" <emacs-devel@gnu.org>
Subject: Re: Allowing rolling release packages on ELPA
Date: Mon, 24 Oct 2022 11:07:14 +0300 [thread overview]
Message-ID: <bdf317ca-01bc-4b2e-8eef-7d34aa5748a8@app.fastmail.com> (raw)
In-Reply-To: <7c2bdbbd-bd23-cda9-50d4-23c4702215df@secure.kjonigsen.net>
[-- Attachment #1: Type: text/plain, Size: 2298 bytes --]
Well the argument about MELPA is a bit misplaced, as there's also MELPA Stable. I mean snapshots are not a bad idea if you know what you're doing (I'm using MELPA myself), but most packages still have "stable" releases. I can't think of a single package that I use that doesn't get tagged releases from time to time.
I was also under the impression that there are already ELPA and NonGNU devel repositories that behave like MELPA, so I'm not sure what would we be solving then.
> Every patch is probably a feature or a bug-fix to some aspect of the package. As a user, I want those as soon as they are
> available.
Often that's not the case - patches can be improvements to docs, build infrastructure, small steps towards some new features, etc.
> Not having to version things manually is a god-send.
It saves a tiny bit of time for the maintainers and makes life a bit harder for the end users IMO. Anyways, perspective on this subject will always vary. For me updating a couple of version numbers in a package is an insignificant amount of work (and it's work that's trivial to automate).
On Mon, Oct 24, 2022, at 9:45 AM, Jostein Kjønigsen wrote:
> 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.
>
> It works fine.
>
>> should something like a change to the docs really result in a new release?
> Yes. Unconditionally.
>
> Every patch is probably a feature or a bug-fix to some aspect of the package. As a user, I want those as soon as they are available.
>
>> 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.
>
>>
>> How much was the demand for something like this in general? I can't think of any major Emacs package that does rolling releases.
> All of them does, if they're on MELPA. That's what MELPA does.
>
> --
>
> Jostein
>
[-- Attachment #2: Type: text/html, Size: 3374 bytes --]
next prev parent reply other threads:[~2022-10-24 8:07 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 [this message]
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
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=bdf317ca-01bc-4b2e-8eef-7d34aa5748a8@app.fastmail.com \
--to=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.