Update open-vm-tools SRU exception#667
Open
athos-ribeiro wants to merge 4 commits into
Open
Conversation
athos-ribeiro
requested review from
RAOF,
basak,
enr0n,
julian-klode,
panlinux and
tjaalton
as code owners
When the most recent Ubuntu supported release is an LTS, we want to be able to backport its version to LTS-1 through this policy exception.
When one wants to fix additional bugs when using the open-vm-tools exception, those additional bugs must be treated as regular SRUs.
athos-ribeiro
force-pushed
the
open-vm-tools
branch
from
99c80a8 to
6743e1d
Compare
Collaborator
Author
|
I applied Renan's change request and rebased it against main. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This originated from the review in https://code.launchpad.net/~rr/ubuntu/+source/open-vm-tools/+git/open-vm-tools/+merge/507103.
The current exception is ambiguous or misleading when it tries to address what backporting means.
Are we supposed to backport the entire package from the most recent supported Ubuntu version or do we want to backport only the upstream pristine tarball, and not the packaging changes?
After discussing this with @renanrodrigo , we understand it should refer to the latter. Therefore, I am applying the changes presented here to reflect that, including some examples to hopefully make it clear.
I am also including an additional clause to the exception to allow these backports to
LTS - 1whenever the most recent supported Ubuntu release is an LTS.