On 08/19/2016 09:20 AM, Kai Engert wrote: > On Fri, 2016-08-19 at 09:01 -0400, Stephen Gallagher wrote: >> With my FESCo hat on, I'd be in favor of landing this in updates-testing >> immediately. Then folks who install the Alpha will get it in their first >> update >> and we'd have ample time to work out the issues prior to Beta. > > If we agree to try to include it with Fedora 25, then both before Alpha and > after Alpha are fine with me. > So, I forgot to include some useful information about Fedora pre-releases. (I have a bad habit of forgetting that not everyone knows all the little details). What I am concerned about is *specifically* the frozen set of packages that becomes part of the Alpha release. As we are already late for shipping that, I'm opposed to increasing the set of things that *might* go wrong (even if the risk is remote). However, pre-release Fedora is different from released Fedoras in that the updates-testing repo is enabled by default on them. This means that if you push the ca-certificates package to updates-testing before next week's Go/No-Go meeting, it is guaranteed that it will already be available to anyone doing a dnf update from the moment they install the Alpha media. This makes it exactly one update from inclusion on Alpha systems. It does not need to wait for a stable push to get there.
Attachment:
signature.asc
Description: OpenPGP digital signature
-- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://lists.fedoraproject.org/admin/lists/devel@xxxxxxxxxxxxxxxxxxxxxxx