Clarification on requirements for a release

Ben Cooksley bcooksley at
Tue Jul 4 07:41:56 UTC 2017

On Tue, Jul 4, 2017 at 7:20 PM, Harald Sitter <sitter at> wrote:
> On Tue, Jul 4, 2017 at 2:49 AM, Ben Cooksley <bcooksley at> wrote:
>> I was the one who made that decision
> Cool
> You are not my supervisor.

Please bear in mind you were the one (if my memory is correct) who
pushed for everyone to include *.asc signatures with every released
tarball, something which *doubles* the amount of effort required of
Sysadmin to perform our part of the release process for essentially
all Extragear and Playground projects.

As I previously mentioned, some software was essentially acting as if
it were production ready while still being in playground which is why
it was necessary to start prompting developers to enter their software
in for review.

In terms of the "chore" of releasing tarballs, the only part we
require is two things which aren't exactly time consuming: upload to
incoming, create ticket with the destination and a list of files and
hashes. You have to do at least one of those regardless of the setup
anyway (given you require a *.asc signature) so I don't see the issue


More information about the release-team mailing list