Re: F30 security update submitted for stable "marked obsolete" instead of being pushed

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

 



On Fri, 29 May 2020 16:55:37 +0200, Kevin Kofler wrote:

> Miro Hrončok wrote:
> > AFAIK this was never the case, but I'm not sure. I remember in the past
> > the updates just kinda stuck in limbo (being pushed to stable for
> > eternity). At least now they are marked as obsolete.  
> 
> I think there really ought to be a guarantee that everything queued before 
> the deadline actually gets pushed in one last push, as opposed to saying 
> "sorry, the last push was actually hours earlier than the official deadline, 
> you're screwed forever because we will never do a push again for that 
> release".

With a properly implemented deadline, the Updates System would close its
doors at a well-defined time prior to a last push. Anything that has entered
the "pending -> stable" queue early enough, would be pushed. Everything else
would be locked and would not be able to change state from testing to stable,
for example.
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [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