[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Automake maintenance
From: |
Mathieu Lirzin |
Subject: |
Re: Automake maintenance |
Date: |
Wed, 04 Jan 2017 12:17:29 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) |
Hi,
Thomas Martitz <address@hidden> writes:
> Am 03.01.2017 um 21:24 schrieb Stefano Lattarini:
>>
>>> On the other hand, any maintainer is better than no maintainer.
>>>
>> Absolutely! Even just having someone operating in maintenance mode
>> would be far better than the current status, in which even the most basic
>> patches, typofixes and bug reports get ignored.
>>
>>> Since my dayjob depends on Automake I could probably devote some
>>> small but fixed amount of time to Automake maintenance.
>>>
>>> Best regards.
>>>
>>
>> Thank you for your interest and patience.
>>
>> Cheers,
>> Stefano
>>
>
> Okay. So I'm wondering about two more things:
>
> 1) What implications does it have to be a maintainer of a GNU
> package. I'm not otherwise connected to GNU. I have completed the
> copyright paperwork for this patch. What other implications or
> requirements are there?
>
> 2) How do you make releases? (preparations in git, where/how to upload
> the tarball, signing the tarball)
Here is a quick introduction for new maintainer:
https://www.gnu.org/software/maintainer-tips
The following link extensively document most of the questions you might
have regarding GNU and the release process:
https://www.gnu.org/prep/maintain/maintain.html
For Automake specific release process, you can take a look at HACKING in
the repo.
Best regards.
--
Mathieu Lirzin
GPG: F2A3 8D7E EB2B 6640 5761 070D 0ADE E100 9460 4D37