Release version 3.2.0
hcho3 opened this issue · comments
Blockers
Release Process
-
Check that the latest CI run on the
mainline
branch is passing. To check, go to the "Actions" tab and look at the scheduled CI jobs that ran today. (We run scheduled CI jobs once every day.)
-
Check out the latest
mainline
branch of Treelite on a local machine. -
Create
release_3.2
branch:git switch -c release_3.2
-
Create a new commit to bump the version to 3.2.0. The following files should be changed:
-
cmake/Python_version.in
: Remove the-dev
suffix. -
python/treelite/VERSION
andruntime/python/treelite_runtime/VERSION
: Change to3.2.0
. -
runtime/java/treelite4j/pom.xml
: Change theversion
field to3.2.0
.
-
-
Push the updated
release_3.2
branch to GitHub:git push origin release_3.2
. -
Check that the CI pipeline runs successfully with the new branch
release_3.2
. The CI pipeline will upload artifacts to an S3 bucket. -
Assign the git tag
3.2.0
to the latest commit of branchrelease_3.2
:git tag 3.2.0
-
Publish the tag to GitHub:
git push origin 3.2.0
. -
Run the Python script
dev/prepare-pypi-release.py
to download the artifacts from the S3 bucket. -
Upload the artifacts to PyPI.
-
Create a new release on GitHub using the tag
3.2.0
. -
Submit a pull request to Treelite to bump the development version to
3.9.0-dev
.-
CMakeLists.txt
: Change line 3 toproject(treelite LANGUAGES CXX C VERSION 3.9.0)
-
python/treelite/VERSION
andruntime/python/treelite_runtime/VERSION
: Change to3.9.0-dev
. -
runtime/java/treelite4j/pom.xml
: Change theversion
field to3.9.0-SNAPSHOT
.
-
-
Submit a pull request to conda-forge/treelite-feedstock to publish the 3.2.0 release to Conda-Forge.