[Bug 2009949] Re: Bionic end-of-LTS date is now May 31st

[Dimitri John Ledkov]

*** This bug is a duplicate of bug 2003949 ***
    https://bugs.launchpad.net/bugs/2003949

@ Renan Rodrigo (renanrodrigo)

There has been extensive discussion and agreement for the dates that
have already been implemented by foundations in distro-info-data and
released in Lunar.

The changes there were extensively discussed and agreed, and whilst
there was broad agreement to document overlap end of standard & esm
supports, there was no discussion that i am aware of to extend the
overall esm-eol dates to 10y + 1 month.

Are you sure this is not duplicate work, and what you really after is to
ensure that backports of
https://bugs.launchpad.net/ubuntu/+source/distro-info-data/+bug/2003949
are accepted into the stable releases?

Do dates in Lunar, satisfy you and whoever requested these changes once
again?

** This bug has been marked a duplicate of bug 2003949
   Document ESM overlap period

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to distro-info-data in Ubuntu.
https://bugs.launchpad.net/bugs/2009949

Title:
  Bionic end-of-LTS date is now May 31st

Status in distro-info-data package in Ubuntu:
  New
Status in distro-info-data source package in Bionic:
  New

Bug description:
  [ Impact ]

  Ubuntu 18.04 Bionic Beaver had its eol-related ("eol", "eol-server",
  "eol-esm") dates bumped to May 31st. This change needs to hit Bionic
  systems, so the software running on those systems may interpret it
  correctly and behave accordingly.

  [ Test Plan ]

  On a bionic system:
  - run `distro-info --date 2023-05-31 --supported`, and check bionic is not listed in the output.
  - install a version of distro-info-data which has the updated dates
  - run `distro-info --date 2023-05-31 --supported`, and check bionic is listed in the output.
  - run `distro-info --date 2023-06-01 --supported`, and check bionic is not listed in the output.

  
  [ Where problems could occur ]

  Wrong dates in the CSV lead to all software depending on it crashing (if the format is wrong, for instance) or behaving in a different way than intended.
  A close review of the date and format (as this is a simple change) can make this change safe enough.
  why

  [ Other Info ]

  On devel, the "eol-esm" is the only date that needs adjustment; all
  eol fields need adjustment on bionic-devel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/distro-info-data/+bug/2009949/+subscriptions