From: Gregory Chamberlain <greg@cosine.blue>
To: Philip Kaludercic <philipk@posteo.net>
Cc: Gregory Chamberlain's Public Inbox <~chambln/public-inbox@lists.sr.ht>
Subject: Re: Adding the Aircon theme to NonGNU ELPA
References: <87wnf5bqv5.fsf@posteo.net> <877d6scgyz.fsf@cosine.blue>
	<87pmkjyig7.fsf@posteo.net> <87mtflh3hm.fsf@cosine.blue>
	<87bkv7vv7p.fsf@posteo.net>
Date: Tue, 07 Jun 2022 07:16:22 +0100
In-Reply-To: <87bkv7vv7p.fsf@posteo.net> (Philip Kaludercic's message of "Sun,
	05 Jun 2022 18:08:58 +0000")
Message-ID: <87wndtj8w9.fsf@cosine.blue>
MIME-Version: 1.0
Content-Type: text/plain

Philip Kaludercic <philipk@posteo.net> writes:

>>> Unless you have already signed the FSF copyright assignment, you should
>>> fill it out and send it to the right address:
>>>
>>> Other than that, I can take care of all the remaining stuff.  If you
>>> decide against wanting to sign the CA, I can also add the package to
>>> NonGNU ELPA.
>>
>> Thanks, I've now sent the CA.
>
> Have you received any update?

Yes, the copyright assignment was completed yesterday. You can add the
Aircon theme to GNU ELPA now.

I am still improving the theme from time to time, pushing updates to the
repository at the URL below.

https://git.sr.ht/~chambln/aircon-theme.el

Occasionally I tag a commit as a new version, but these "releases" are
somewhat arbitrary. Although changes have been incremental for a while
now, I'm reluctant to call it stable just yet.

What is the process of a new release making its way to GNU ELPA? How
closely do GNU ELPA packages follow upstream releases?