Skip to content
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

Run K2 using 2.0.0-Beta2 #3327

Merged
merged 2 commits into from
Dec 20, 2023
Merged

Run K2 using 2.0.0-Beta2 #3327

merged 2 commits into from
Dec 20, 2023

Conversation

serras
Copy link
Member

@serras serras commented Dec 20, 2023

I think we should stop tracking the -dev versions of 2.0, and just use the beta's, since this is what our users are ultimately going to see

Copy link
Member

@nomisRev nomisRev left a comment

Choose a reason for hiding this comment

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

Sounds good to me! I thought we were able to track the latest DEV/EAP and build against that to help track down regression but building against Beta2 sounds good for me ☺️

@serras
Copy link
Member Author

serras commented Dec 20, 2023

Sounds good to me! I thought we were able to track the latest DEV/EAP and build against that to help track down regression but building against Beta2 sounds good for me ☺️

I think that made sense when this was the only way to track 2.0. However, it's becoming increasingly difficult to keep up with all the dependencies (especially some like KSP), and I think this provides a good middle ground.

Copy link
Contributor

Kover Report

Total Project Coverage 54.56%

@serras serras merged commit a685f01 into main Dec 20, 2023
11 checks passed
@serras serras deleted the serras/k2-beta-2 branch December 20, 2023 12:33
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