From: Stephen Leake <stephen_leake@stephe-leake.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: ELPA ada-mode.release not updating
Date: Mon, 24 Oct 2022 10:38:02 -0700 [thread overview]
Message-ID: <86v8o9i0lh.fsf@stephe-leake.org> (raw)
In-Reply-To: <jwveduxz1tl.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Mon, 24 Oct 2022 11:25:25 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> Stephen Leake [2022-10-24 02:47:06] wrote:
>> I pushed a commit to bump the version of ada-mode to 4.3.0 41 hours ago,
>> but https://elpa.gnu.org/packages/ada-mode.html still shows 4.2.1.
>> What's wrong?
>
> [ Hmm... I must be missing something. In my world,
> https://elpa.gnu.org/packages/ada-mode.html shows version `7.2.1` and
> elpa.git has version `7.3.beta1`. I'll assume some gremlin swapped
> the 4 and 7 keys on your keyboard. ]
Yes, sorry about that.
> We don't consider `7.3.beta1` as a "release", so elpa.gnu.org generated
> a tarball only for GNU-devel.
Hmm. I guess you mean the changes from 7.2.1 to 7.3.beta1, and then
to 7.3.0, are not sufficient to trigger a release of ada-mode in
non-devel ELPA?
I could not find the actual code in elpa-admin that makes that decision;
could you point me to it?
So I need to bump it again, to 7.3.1?
--
-- Stephe
next prev parent reply other threads:[~2022-10-24 17:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-24 9:47 ELPA ada-mode.release not updating Stephen Leake
2022-10-24 15:25 ` Stefan Monnier
2022-10-24 17:33 ` Stefan Monnier
2022-10-24 21:00 ` Stephen Leake
2022-10-25 2:38 ` Stephen Leake
2022-10-25 17:46 ` Stefan Monnier
2022-10-26 13:50 ` Stephen Leake
2022-10-26 15:04 ` Stefan Monnier
2022-10-26 19:00 ` Stephen Leake
2022-10-24 17:38 ` Stephen Leake [this message]
2022-10-24 21:12 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86v8o9i0lh.fsf@stephe-leake.org \
--to=stephen_leake@stephe-leake.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 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.