On 11/25/2016 04:36 PM, James Hogarth wrote:
On 25 November 2016 at 14:15, Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx> wrote:
On Fri, Nov 25, 2016 at 12:24:40PM +0100, Michael Schwendt wrote:
For the release of F25, has nobody run the upgrade path violations checker
to warn packagers about any downgrades the dist update would perform?
A missing zero day update [only available in updates-testing] for Claws
Mail has hit users. Not great. And I hear there are other packages that
get downgraded when upgrading to F25.
It seems like we should gate updates so that upgrade order is always
preserved.
This is an unfortunate downside of the present freeze process to an extent ...
I'm honestly not sure what the best option here is ...
IMHO, it would be best to launch the "post-release" package process the
very moment the freeze becomes active.
I.e.
* Before the freeze, packages would go
"updates-testing" -> "main"
* During the freeze, packages would go
"updates-testing" -> "updates"
with rel-eng cherry-picking individual packages from "updates" and move
them to "main" to compose the "release".
* After the release, packages would go
"updates-testing" -> "updates"
as before.
This would allow packagers to continue their works in all phases of
release preparations without lockouts, delays and upgrade path violations.
It would also avoid the usual "flood of updates", commonly Fedora
experiences in early post release weeks.
Ralf
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx