On Mon, Feb 06, 2017 at 08:38:04AM -0500, Matthew Miller wrote:
On Sun, Feb 05, 2017 at 09:12:26PM +0100, Hans de Goede wrote:
> >* Why is it not proposed for F26 (now the deadline is over, but IMHO it
> >should get in)?
>
> Since the plan has always been (as that page shows) to get it into F25,
> which would not make it a F26 change.
There's a big Change process question here which I think FESCo should
resolve. If a Change does not meet the deadline, should it be released
as an update, automatically retargetted for the next release, or need
to be re-proposed? I think probably all answers of these possibilities
are appropriate for some cases; maybe we should make "if you didn't
make the deadlines, please run past fesco for what to do next" part of
the process.
Hi,
My POV is that if a Change does not meet the deadline needs _always_
to be re-proposed.
Fale
--
Fabio Alessandro Locati
Red Hat - Senior Consultant
PGP Fingerprint: E815 3C49 2A8D FD8B 1CBD BC85 FDB3 DF20 B2DC 9C1B