On Pá, 2016-08-19 at 15:54 +0200, Kai Engert wrote:
> On Fri, 2016-08-19 at 09:45 -0400, Stephen Gallagher wrote:
> >
> > 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.
> Thank you for this detail.
>
> In other words:
> - exclude this change from alpha to avoid all risks
> - create the alpha release, and after it's done:
> - build this change into f25 updates-testing
> - all F25 alpha users doing updates will get this change
> immediately and will participate in testing it.
+1 to this plan, except for one thing - you do not have to wait for
alpha to be released before you build and create the testing update. It
will not be inadvertently included into the alpha anyway.
--
Tomas Mraz
No matter how far down the wrong road you've gone, turn back.
Turkish proverb
(You'll never know whether the road is wrong though.)
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://lists.fedoraproject.org/admin/lists/devel@xxxxxxxxxxxxxxxxxxxxxxx
