Hendrik/xgboost
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

[doc] Additional notes for release [skip ci] (#8367)

Browse Source
This commit is contained in:
Jiaming Yuan 2022-10-26 17:55:15 +08:00 committed by GitHub
parent cf70864fa3
commit 786aa27134
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
doc/contrib/release.rst
View File

@ -17,14 +17,18 @@ Making a Release
----------------- -----------------
1. Create an issue for the release, noting the estimated date and expected features or major fixes, pin that issue. 1. Create an issue for the release, noting the estimated date and expected features or major fixes, pin that issue.
2. Bump release version. 2. Create a release branch if this is a major release. Bump release version.
1. Modify ``CMakeLists.txt`` in source tree and ``cmake/Python_version.in`` if needed, run CMake. 1. Modify ``CMakeLists.txt`` in source tree and ``cmake/Python_version.in`` if needed, run CMake.
2. Modify ``DESCRIPTION`` in R-package. If this is a RC release, the Python version has the form <major>.<minor>.<patch>rc1
2. Modify ``DESCRIPTION`` and ``configure.ac`` in R-package. Run ``autoreconf``.
3. Run ``change_version.sh`` in ``jvm-packages/dev`` 3. Run ``change_version.sh`` in ``jvm-packages/dev``
If this is a RC release, the version for JVM packages has the form <major>.<minor>.<patch>-RC1
3. Commit the change, create a PR on GitHub on release branch. Port the bumped version to default branch, optionally with the postfix ``SNAPSHOT``. 3. Commit the change, create a PR on GitHub on release branch. Port the bumped version to default branch, optionally with the postfix ``SNAPSHOT``.
4. Create a tag on release branch, either on GitHub or locally. 4. Create a tag on release branch, either on GitHub or locally.
5. Make a release on GitHub tag page, which might be done with previous step if the tag is created on GitHub. 5. Make a release on GitHub tag page, which might be done with previous step if the tag is created on GitHub.