Changes
Page history
Update How to prepare the code for a release
authored
Dec 16, 2024
by
Alexis GAMELIN
Hide whitespace changes
Inline
Side-by-side
How-to-prepare-the-code-for-a-release.md
View page @
ea35e868
Here is the checklist to run before releasing a new version for mbtrack2:
Here is the checklist to run before releasing a new version for mbtrack2:
1.
Create a new local branch from the merge develop (with all the feature branch intended to be included in the new version).
1.
Create a new local branch from the merge develop (with all the feature branch intended to be included in the new version).
2.
Update readthedocs documentation
2.
Update
.rst for the
readthedocs documentation
3.
Book a new zenodo DOI and update readme.md and __init__.py
3.
Book a new zenodo DOI and update readme.md and __init__.py
4.
Update the pyproject.toml file with version number, new dependencies and so on.
4.
Update the pyproject.toml file with version number, new dependencies and so on.
5.
Update README.md
5.
Update README.md
...
@@ -23,4 +23,5 @@ Here is the checklist to run before releasing a new version for mbtrack2:
...
@@ -23,4 +23,5 @@ Here is the checklist to run before releasing a new version for mbtrack2:
9.
Publish on pypi:
9.
Publish on pypi:
*
`poetry config http-basic.pypi __token__ api_token`
*
`poetry config http-basic.pypi __token__ api_token`
*
`poetry publish`
*
`poetry publish`
10.
Add zip archive of stable to zenodo
10.
Add zip archive of stable to zenodo
\ No newline at end of file
11.
Rebuild docs on the https://app.readthedocs.org/ website
\ No newline at end of file