Stefan Monnier <monnier@iro.umontreal.ca> writes:

> Stefan Monnier [2022-10-24 11:25:25] wrote:
>> 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.  ]
>>
>> We don't consider `7.3.beta1` as a "release", so elpa.gnu.org generated
>> a tarball only for GNU-devel.
>
> Oh, I think I understand what's going on.  You're using
> a `:release-branch` thingy, but this specifies the release branch of the
> upstream Git repository, whereas `ada-mode` doesn't have an
> upstream repository.
>
> For packages with a nil `:url`, the `:release-branch` happens to act
> only as a boolean and the branch from which the code is fetched is
> always `externals-release/<PKG>` for GNU ELPA and `elpa-release/<PKG>`
> for NonGNU ELPA.
>
> For some reason, the fact that there is no such branch for `ada-mode`
> did not cause any error to be emitted in the cron job's reports :-(

Ok, I've pushed externals-release/ada-mode and externals-release/wisi,
and deleted the other branches.

Attached is a patch for README; ok to commit?

-- 
-- Stephe