Re: Any chance to make a new autoconf release?

[Eric Blake]

On 3/5/19 3:01 PM, Nicholas Clark wrote:
> So let's say somebody from the community wanted to cut a new Autoconf
> release. How would they go about doing it?

HACKING gives a nice overview, but a good first hurdle to clear is to at
least prove that you are capable of submitting patches (such as a patch
to bump the copyright year to 2019, or to fix the testsuite failures
that have been reported when using bash 5). The set of developers that
have savannah push rights (and can thus upload a new tarball) is small,
and I'm unlikely to hand that out to anyone that has not at least first
shown on the list that they are trying to improve the current state of
things with working patches.

-- 
Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3226
Virtualization:  qemu.org | libvirt.org

signature.asc
Description: OpenPGP digital signature