This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: glibc 2.25 development --- 46 days to freeze.
On 12/02/2016 01:15 PM, Siddhesh Poyarekar wrote:
> On Friday 02 December 2016 09:24 PM, Carlos O'Donell wrote:
>> Do you have registered gpg keys to upload for glibc?
>
> I'm not sure what you mean by registered, but I have uploaded my gpg key
> to a keyserver:
>
> https://keys.fedoraproject.org/pks/lookup?op=vindex&search=0x79C43DFBF1CF2187
That is not sufficient.
You must register your key with the FSF servers to do the upload:
https://www.gnu.org/prep/maintain/html_node/Automated-Upload-Registration.html#Automated-Upload-Registration
While I think _you_ should definitely get you key authorized to do
uploads, I don't think that *all* release managers should need to
go through the process of registering their keys. For example I think
all the distro maintainers should be able to run through a release
manager cycle without having to have their GPG key registered with
the FSF to do the upload. I think a core of senior developers can
do all the uploads as required. I'm not saying this to exclude anyone,
but just limit (a) the risk of everyone being to upload a release and
(b) the annoyance of having to go through that process and maintain
a key.
Thoughts?
--
Cheers,
Carlos.