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

Add administrative tasks for releasing 4C #253

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

amgebauer
Copy link
Member

@amgebauer amgebauer commented Jan 14, 2025

Currently draft, since the exact procedure might not be final.

We might want to automate step 6.

@4C-multiphysics/maintainer

@amgebauer amgebauer force-pushed the add-release-administrative-tasks branch 2 times, most recently from 727de3c to d7caa59 Compare January 14, 2025 15:25
@amgebauer amgebauer force-pushed the add-release-administrative-tasks branch from d7caa59 to 5560a02 Compare January 14, 2025 15:28
Copy link
Member

@sebproell sebproell left a comment

Choose a reason for hiding this comment

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

I think the necessary steps are well documented 👍 let's merge this

.. note::
For a PATCH-release, only the steps 4 to 6 are necessary. Commits are typically added to the ``main``
branch and cherry-picked to the release branch. That ensures that the main branch is fixed and the
PATCH itself is still comptabile with all projects consuming a specific version of |FOURC|.
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
PATCH itself is still comptabile with all projects consuming a specific version of |FOURC|.
PATCH itself is still compatible with all projects consuming a specific version of |FOURC|.

This reminds me of #240 :)

@amgebauer
Copy link
Member Author

I will discuss this with @ppraegla once he is back. I want to automate step 6, otherwise we will never do it.

@amgebauer
Copy link
Member Author

After step 6, we also need to:

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