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

introduce mcs-devel.xml #20

Merged
merged 4 commits into from
Jul 18, 2024
Merged

introduce mcs-devel.xml #20

merged 4 commits into from
Jul 18, 2024

Conversation

lsf37
Copy link
Member

@lsf37 lsf37 commented Jul 18, 2024

The idea is that mcs.xml takes the role default.xml has on the master branch, and mcs-devel.xml the role of devel.xml.

Version bump script and CI still need to be updated, but we can start by merging this PR and updating our repo checkouts.

lsf37 added 3 commits July 18, 2024 15:08
This will be the default development manifest for the mcs branch, and
mcs.xml will take the role default.xml has for the master branch.

Signed-off-by: Gerwin Klein <[email protected]>
@lsf37 lsf37 self-assigned this Jul 18, 2024
Copy link
Member

@Xaphiosis Xaphiosis left a comment

Choose a reason for hiding this comment

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

I admit I didn't consider the difference between default.xml and devel.xml before, only ever using the former. I approve of consistency between mcs and non-mcs.

@lsf37 lsf37 merged commit 8803ec1 into master Jul 18, 2024
6 checks passed
@lsf37 lsf37 deleted the mcs-devel branch July 18, 2024 06:26
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.

4 participants