On Wednesday, November 13th, 2024 at 18:48, Fabio Valentini <decathorpe@xxxxxxxxx> wrote: > > > On Sun, Nov 10, 2024 at 10:16 AM Pavel Solovev daron439@xxxxxxxxx wrote: > > > Due to never-ending "config refactors" it's difficult to push an update and not to violate https://docs.fedoraproject.org/en-US/fesco/Updates_Policy. I'm in favour of a rolling release approach and I don't want to be the one to keep a year old packages in the repo. > > > You could request an Updates Policy exception if supporting old > versions in stable branches isn't feasible ... > But to be honest this sounds like the projects are just not mature > enough to be shipped in non-rolling-release distributions? > > Fabio > -- > _______________________________________________ > 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 > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue If you really don't want to continue maintaining despite Fabio's suggestion, I would take over maintaining hyprland because I use it. The project seems to release a major update every 1-2 months. And it seems to have breaking changes every 2nd update. -- _______________________________________________ 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
