Skip to content

docs: package-upgrade-solution #229

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: trunk
Choose a base branch
from

Conversation

XavierChanth
Copy link
Member

- What I did

  • ADR for package upgrade solutions

- How I did it

- How to verify it

- Description for the changelog
docs: package-upgrade-solution

@XavierChanth XavierChanth requested a review from cpswan February 4, 2025 17:11
Copy link
Member

@cpswan cpswan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We need to converge on a recommendation before proceeding with this.

@XavierChanth
Copy link
Member Author

We need to converge on a recommendation before proceeding with this.

I don't mind setting aside some free time to explore option 3. It would be nice to have a tool that allows us to be in control of our own upgrade policies.

@XavierChanth XavierChanth force-pushed the package-upgrade-solution branch 2 times, most recently from a7c3b27 to efd884e Compare February 12, 2025 16:55
@XavierChanth XavierChanth force-pushed the package-upgrade-solution branch from efd884e to 805b177 Compare April 22, 2025 05:27
Copy link
Member

@cpswan cpswan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My vote is for option 2.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants