Why different keys for -testing and non-testing?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Currently we have two gpg keys per release, one for
rawhide/updates-testing and one for the final release and stable
updates.  This complicates a number of things and I'm really wondering
what is the real actual value we get out of having multiple keys per
release?  I have some ideas that I'm going to keep to myself for right
now, but I'd like you, the consumers to help me understand what value
you see in it, and if that value remains if we were to have a key we
applied to all koji builds as the happen which is different from the
'release' key we'd use at release time and updates(-testing?) time for
each release.

-- 
Jesse Keating
Fedora -- Freedom² is a feature!
identi.ca: http://identi.ca/jkeating

Attachment: signature.asc
Description: This is a digitally signed message part

-- 
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux