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
1 year ago
by
Alexis GAMELIN
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
How-to-prepare-the-code-for-a-release.md
+2
-2
2 additions, 2 deletions
How-to-prepare-the-code-for-a-release.md
with
2 additions
and
2 deletions
How-to-prepare-the-code-for-a-release.md
View page @
b7c993fd
...
...
@@ -13,8 +13,8 @@ Here is the checklist to run before releasing a new version for mbtrack2:
*
`poetry build`
*
Test build on test pypi:
*
`poetry config repositories.test-pypi https://test.pypi.org/legacy/`
*
`poetry config http-basic.test-pypi
<username> <password>
`
*
`poetry publish test-pypi`
*
`poetry config http-basic.test-pypi
__token__ api_token
`
*
`poetry publish
-r
test-pypi`
*
Install in a clean virtual environment (e.g. google colab) to check that it is ok using:
*
`pip install --index-url https://test.pypi.org/simple/ --extra-index-url https://pypi.org/simple mbtrack2`
8.
Merge to stable with a new tag and changelog.
...
...
This diff is collapsed.
Click to expand it.