From: Tassilo Horn <tsdh@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: How to do a beta release on ELPA?
Date: Fri, 30 Oct 2020 21:32:37 +0100 [thread overview]
Message-ID: <87361vpi8q.fsf@gnu.org> (raw)
In-Reply-To: <jwvo8koohmq.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Mon, 26 Oct 2020 16:49:24 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
Hi Stefan,
>> I don't think there are too many people running straight from our
>> master branch, so I guess we should do a new ELPA release pretty soon
>> to get more testing. But is there a way to release a new ELPA
>> version just for the adventurous?
>
> Not really, no.
Ok, I guessed so.
> I'd like to create an alternative ELPA archive built from elpa.git but
> using the latest code (kind of like the non-stable Melpa), but that's
> been a TODO item for a while already and I've not even tried to get
> started on it.
You gotta have plans.
>> 2) Just do a normal ELPA release and if things break for some users tell
>> them how to pin auctex to version 12.3.1 for the time needed to fix
>> their issues.
>
> That's what I'd recommend, yes.
> I'd definitely give it a release version that sounds like "major
> release". We're way past "2.0", so I'll let you find the next best
> choice.
Yes, we'll release it as GNU AUCTeX 13.0.0 on ELPA and when things have
stabilized, we'll do a 13.1 tarball release. So the current version 12
is the last one of the pre-lexical-binding era.
>> With option 2), I guess it could harm users who don't know how to
>> reach out for help.
>
> Maybe emit a warning during compilation or upon "first use", with an
> appropriate description of the kind of problems that can happen. Many
> users still won't read it, but it increases the chances that they'll
> find someone who has.
Yes, I guess such a first use message pointing to the docs where we
describe exactly what has changed and how to migrate would be a good
solution.
>> Are there any other (preferably better!) options?
>
> Option 1: change the code so as not to introduce such backward
> incompatibilities (e.g. Calendar ended keeping nasty dynamically
> scoped vars like `date` and `month` in order to maximize compatibility
> with existing code). That can't be a 100% solution tho since there
> can always be people who used non-documented vars via dynamic scoping.
Nah, I'm happy those are all gone. :-)
> Option 2: rely on the quick&easy release process: as soon as you hear
> of one incompatibility, you immediately adjust the code (typically to
> mark some var as dynscoped) and make a new minor release.
Yes, that's definitely what we are planning to do and the reason it'll
be on ELPA first.
> Option 3: (getting really creative here) make sure you new code makes
> no other changes than switching to lexical-binding and then do
> temporary release: release 12.3.2 with lexical-binding, then a week
> later release 12.3.3 without lexical-binding (i.e. reverting to the
> previous code) and work on fixing the incompatibilities found along
> the way, then try again with the new&improved lexical-binding code,
> maybe leaving it for a month instead of a week, ...
That's creative indeed!
> If you insist, I'm sure I can come up with an even more fun option 4.
Please stop it! ;-)
Thanks,
Tassilo
next prev parent reply other threads:[~2020-10-30 20:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-24 10:39 How to do a beta release on ELPA? Tassilo Horn
2020-10-26 20:49 ` Stefan Monnier
2020-10-30 20:32 ` Tassilo Horn [this message]
2020-10-30 22:21 ` Stefan Monnier
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87361vpi8q.fsf@gnu.org \
--to=tsdh@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).