This is not ideal; once introduced into main in an LTS release, the implication is that the package will receive security updates for the remaining lifetime of the LTS. I believe there were discussions about this at the time the package was added to trusty-updates, though I don't find any documentation for this now.
On the plus side, there is no Supported: field for the linux-keystone entries in the Packages file. On the minus side, there have been quality issues over time with the Supported: metadata in the archive as well as with the ubuntu-support-status tool, so this distinction is not likely to be well understood by users.
Care should be taken in the future to avoid adding packages to main without clear annotation of support committment, so that users are not led to rely on presumed support periods.
In this instance I can see no justification for keeping the package in the archive given the above statement of non-support.
This is not ideal; once introduced into main in an LTS release, the implication is that the package will receive security updates for the remaining lifetime of the LTS. I believe there were discussions about this at the time the package was added to trusty-updates, though I don't find any documentation for this now.
On the plus side, there is no Supported: field for the linux-keystone entries in the Packages file. On the minus side, there have been quality issues over time with the Supported: metadata in the archive as well as with the ubuntu- support- status tool, so this distinction is not likely to be well understood by users.
Care should be taken in the future to avoid adding packages to main without clear annotation of support committment, so that users are not led to rely on presumed support periods.
In this instance I can see no justification for keeping the package in the archive given the above statement of non-support.