Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
M
mbtrack2
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Iterations
Wiki
Requirements
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Deploy
Releases
Package registry
Model registry
Operate
Terraform modules
Analyze
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
PA
Collective Effects
mbtrack2
Wiki
How to prepare the code for a release
Changes
Page history
New page
Templates
Clone repository
Update How to prepare the code for a release
authored
4 months ago
by
Alexis GAMELIN
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
How-to-prepare-the-code-for-a-release.md
+3
-2
3 additions, 2 deletions
How-to-prepare-the-code-for-a-release.md
with
3 additions
and
2 deletions
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:
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
4.
Update the pyproject.toml file with version number, new dependencies and so on.
5.
Update README.md
...
...
@@ -23,4 +23,5 @@ Here is the checklist to run before releasing a new version for mbtrack2:
9.
Publish on pypi:
*
`poetry config http-basic.pypi __token__ api_token`
*
`poetry publish`
10.
Add zip archive of stable to zenodo
\ No newline at end of file
10.
Add zip archive of stable to zenodo
11.
Rebuild docs on the https://app.readthedocs.org/ website
\ No newline at end of file
This diff is collapsed.
Click to expand it.