#49 add availability date + EOL date to collections list
Opened 6 years ago by zbyszek. Modified 4 years ago

This is a continuation of https://fedorahosted.org/rel-eng/ticket/6081.

https://admin.fedoraproject.org/pkgdb/collections/ contains a list of collections along with status (active/EOL/under development). It would great it this list could be extended with the "start" and "end" dates. This would be useful for upgrades: dnf-plugin-system-upgrade could tell the user that their current release has 1 month of support left, if they upgrade to F22 they will have approx. 6 months of life, if they upgrade to F23 they will have 12 months of life, etc.

This could be useful for other tools. I can imagine a notification popping up "your release of fedora is going EOL in 2 weeks. Consider upgrading."

I understand that the dates would be only projections, but super precise dates aren't really necessary here. If a release slips, previous releases simply get slightly longer life.


I was thinking to simply expose the date of the last change to the collection. So when a collection goes from Under Development to Active we know that Fn-2 has only 2 months left.

This would avoid having the admins to enter precise dates for EOL. You say precise date don't really matter but, a) we can't quite do not precise date in IT :) and b) "your release of fedora is going to be EOL in 3 weeks ago" might not be a nice message to send to our users if we forgot to update the EOL date and the release has slip for few weeks.

Do you think the date_updated is a good compromise for this?

Implemented in https://github.com/fedora-infra/pkgdb2/pull/266

Feel free to comment here or there if this would solve your question.

Any chance we could have actual dates instead, instead of having to do guesswork on the client side?

I'd go with a new "eol_date" field and remove the "date_created" and "date_updated" fields, I don't really think these help in this case.

I don't want to add magical calculations to the client side tools and impose policy when a release should go EOL on client side. The exact date is based on a FESCo/releng decision and is never exactly 1 month after new release.

Login to comment on this ticket.

Metadata