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

Commonalities r2.1 #340

Closed
rartych opened this issue Nov 15, 2024 · 1 comment · Fixed by #342
Closed

Commonalities r2.1 #340

rartych opened this issue Nov 15, 2024 · 1 comment · Fixed by #342
Labels
subproject management Indicating issues with subproject repository or release management process

Comments

@rartych
Copy link
Collaborator

rartych commented Nov 15, 2024

Problem description
For milestone M2 Commonalities should publish Release Candidate

Expected action
The release PR for r2.1 needs to be prepared, when scope of the version 0.5 (documented in #273) is covered.

Additional context
For meta-release Spring25 the target date for M2 is planned for 7th of December 2024: https://lf-camaraproject.atlassian.net/wiki/spaces/CAM/pages/14560849/Meta-release+Spring25#Milestone-status

@rartych rartych added the subproject management Indicating issues with subproject repository or release management process label Nov 15, 2024
@rartych rartych changed the title Commonalities r1.1 Commonalities r2.1 Nov 18, 2024
@rartych
Copy link
Collaborator Author

rartych commented Nov 21, 2024

Update from Release Management - create a first pre-release (alpha) with merged PRs (agreed in the meeting on Nov 25th) by the end of November.
The M2 can be then shifted to cover the full scope defined in #273
@camaraproject/commonalities_codeowners Please review PRs with Spring25 label

@rartych rartych mentioned this issue Nov 21, 2024
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
subproject management Indicating issues with subproject repository or release management process
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant