From: Philip Kaludercic <philipk@posteo.net>
To: Gregory Chamberlain <greg@cosine.blue>
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> <87wndtj8w9.fsf@cosine.blue>
Autocrypt: addr=philipk@posteo.net; prefer-encrypt=nopreference; keydata=
 mDMEYHHqUhYJKwYBBAHaRw8BAQdAp3GdmYJ6tm5McweY6dEvIYIiry+Oz9rU4MH6NHWK0Ee0QlBo
 aWxpcCBLYWx1ZGVyY2ljIChnZW5lcmF0ZWQgYnkgYXV0b2NyeXB0LmVsKSA8cGhpbGlwa0Bwb3N0
 ZW8ubmV0PoiQBBMWCAA4FiEEDM2H44ZoPt9Ms0eHtVrAHPRh1FwFAmBx6lICGwMFCwkIBwIGFQoJ
 CAsCBBYCAwECHgECF4AACgkQtVrAHPRh1FyTkgEAjlbGPxFchvMbxzAES3r8QLuZgCxeAXunM9gh
 io0ePtUBALVhh9G6wIoZhl0gUCbQpoN/UJHI08Gm1qDob5zDxnIHuDgEYHHqUhIKKwYBBAGXVQEF
 AQEHQNcRB+MUimTMqoxxMMUERpOR+Q4b1KgncDZkhrO2ql1tAwEIB4h4BBgWCAAgFiEEDM2H44Zo
 Pt9Ms0eHtVrAHPRh1FwFAmBx6lICGwwACgkQtVrAHPRh1Fw1JwD/Qo7kvtib8jy7puyWrSv0MeTS
 g8qIxgoRWJE/KKdkCLEA/jb9b9/g8nnX+UcwHf/4VfKsjExlnND3FrBviXUW6NcB
Date: Tue, 07 Jun 2022 07:47:31 +0000
In-Reply-To: <87wndtj8w9.fsf@cosine.blue> (Gregory Chamberlain's message of
	"Tue, 07 Jun 2022 07:16:22 +0100")
Message-ID: <87pmjk9ap8.fsf@posteo.net>
MIME-Version: 1.0
Content-Type: text/plain

Gregory Chamberlain <greg@cosine.blue> writes:

> 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.

Great!

> 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.

I would not worry about that, there is no hard definition of stability
that all ELPA packages hold themselves to.  I'd just try my best to not
mark releases with broken or untested code.

> What is the process of a new release making its way to GNU ELPA? How
> closely do GNU ELPA packages follow upstream releases?

The package specification can be configured to synchronise the Git
repository daily, but new versions are released only when the version
tag is bumped.  ELPA does not use Git tags at all.  Between releases you
can check http://elpa.gnu.org/devel/ to see how a package would appear
if published.  You should watch out not to force-push to your default
branch, because otherwise the upstream mirror will diverge and that will
have to be fixed manually.