Re: proposal idea: EOL notifications

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

 



On Wed, Jul 6, 2022 at 11:49 AM Neal Gompa <ngompa13@xxxxxxxxx> wrote:
>
> On Wed, Jul 6, 2022 at 11:45 AM Zbigniew Jędrzejewski-Szmek
> <zbyszek@xxxxxxxxx> wrote:
> >
> > Hi,
> >
> > In https://pagure.io/fesco/issue/2803 Artem asked for a user-visible
> > notification when a Fedora stops being supported. Various proposals
> > for online checks were discussed in the bug, but I think we might make
> > do with something much simpler.
> >
> > https://github.com/systemd/systemd/pull/23924 proposes adding
> > SUPPORT_END=YYYY-MM-DD to /usr/lib/os-release. My idea would that we'd
> > e.g. pop up a desktop notification when that date is close, and a
> > bigger redder notification once it has been passed. The date could be
> > set to some initial value even on the initial release, and then
> > adjusted through updates to fedora-release.rpm if our schedule slips.
> > I guess we could add a notification during boot in systemd itself, but
> > most users wouldn't see that, so a graphical notification would also
> > be needed.
> >
> > The advantage of this proposal that it is very simple and will work
> > even on machines that don't have network connectivity, and can be easily
> > integrated into various DEs and tools.
> >
> > WDYT?
> >
>
> Wouldn't it make sense to have the start date and the time period
> supported instead?

Fedora release lifecycles are not date or timeframe driven.  They are
driven by the N+2 release, which can and does slip which means you
will have stale information in /etc/os-release every time that
happens.  Issuing updates to document these slips seems like a lot of
work for little gain.  Even if you did, disconnected machines also
wouldn't get updates to this.

I really don't think encoding lifecycle information in the
installation itself is the right approach, but it's perhaps the most
tenable one for Fedora.  However, until Fedora definitively moves to
using independent lifecycles for their releases, this is a game of
whack-a-mole.

josh
_______________________________________________
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 on the list, report it: https://pagure.io/fedora-infrastructure




[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