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

[ftr] Prepare release #506

Open
5 of 10 tasks
daniel-jettka opened this issue Dec 18, 2024 · 3 comments
Open
5 of 10 tasks

[ftr] Prepare release #506

daniel-jettka opened this issue Dec 18, 2024 · 3 comments
Assignees
Milestone

Comments

@daniel-jettka
Copy link
Contributor

daniel-jettka commented Dec 18, 2024

Is your feature request related to a problem? Please describe.
Some steps are necessary prior to the release.

Describe the solution you'd like
Necessary steps to prepare the release:

  • create draft in Zenodo -> https://zenodo.org/uploads/14512557
  • get DOI -> 10.5281/zenodo.14512557
  • create release branch -> release/v1.0.0
  • update CITATION.cff (date, contributors)
  • merge develop into release/v1.0.0
  • bump version number
  • test
  • merge release/v1.0.0 to main
  • merge main to develop
  • delete release branch release/v1.0.0

Describe alternatives you've considered
./.

Additional context
./..

@daniel-jettka
Copy link
Contributor Author

daniel-jettka commented Dec 18, 2024

@krHERO krHERO moved this to New in Edirom Development Dec 18, 2024
@bwbohl bwbohl moved this from New to Backlog in Edirom Development Dec 18, 2024
@peterstadler
Copy link
Member

Sounds like a good plan!

I'd only recommend to not "merge release/v1.0.0 to develop" but merge back from main into develop. Otherwise you'll end up with different (merge) commits and the branches are not synced anymore.

@krHERO
Copy link
Member

krHERO commented Jan 10, 2025

integrate solved bugs that were found during testing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Backlog
Development

When branches are created from issues, their pull requests are automatically linked.

3 participants