Indicate support lifetimes for individual packages
Bug #1958807 reported by
Jānis Kangarooo
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
Low
|
Unassigned | ||
Bug Description
Show bug report selected affected distro version info when is real EOL Otherwise people for Ubuntu packages assume they wont be fixed in Kubuntu even if both use same main sources of Ubuntu fixed packages by somehat guaranteed support of porting from debian, while a lot can be fixed by non-supporters, so people can still fix EOL 5 year and see paid 10y service packages.
Revision history for this message
| Colin Watson (cjwatson) wrote | #1 |
| tags: | added: feature lp-bugs |
| summary: |
- Show bug report selected affected distro version info when is real EOL - Otherwise people for Ubuntu packages assume they wont be fixed in - Kubuntu even if both use same main sources of Ubuntu fixed packages by - somehat guaranteed support of porting from debian, while a lot can be - fixed by non-supporters, so people can still fix EOL 5 year and see paid - 10y service packages. + Indicate support lifetimes for individual packages |
| Changed in launchpad: | |
| status: | New → Triaged |
| importance: | Undecided → Low |
To post a comment you must log in.
"Somewhat guaranteed support of porting from Debian" is no such thing. The process of syncing packages from Debian makes a big difference for the Ubuntu development release, certainly, but it's not used for updating Ubuntu stable releases, and it's almost exactly as much work to (for example) grab a fix from Debian and put it through the Ubuntu stable release update process as it is to grab a fix from upstream and do the same thing.
I agree that we should model the support lifetimes for individual packages so that it's easier to see what you can expect (though this is a fairly big job).