DBZ-3918 Removing reference to development_docs branch
This commit is contained in:
parent
6a4896d2d4
commit
26921a9836
14
RELEASING.md
14
RELEASING.md
@ -93,20 +93,6 @@ This should report:
|
|||||||
|
|
||||||
Only if this is the case can you proceed with the release.
|
Only if this is the case can you proceed with the release.
|
||||||
|
|
||||||
## Rebase and merge development docs branch
|
|
||||||
|
|
||||||
The documentation of the current development version is published from the `development_docs` branch,
|
|
||||||
which always is based off of the latest development release tag.
|
|
||||||
|
|
||||||
The branch may contain critical documentation updates for the development release documentation,
|
|
||||||
which couldn't wait until the next release.
|
|
||||||
In this case rebase the branch to the current master and merge it:
|
|
||||||
|
|
||||||
$ git checkout development_docs
|
|
||||||
$ git rebase master
|
|
||||||
$ git checkout master
|
|
||||||
$ git merge development_docs
|
|
||||||
|
|
||||||
## Update versions and tag
|
## Update versions and tag
|
||||||
|
|
||||||
Once the codebase is in a state that is ready to be released, use the following command to automatically update the POM to use the release number, commit the changes to your local Git repository, tag that commit, and then update the POM to use snapshot versions and commit to your local Git repository:
|
Once the codebase is in a state that is ready to be released, use the following command to automatically update the POM to use the release number, commit the changes to your local Git repository, tag that commit, and then update the POM to use snapshot versions and commit to your local Git repository:
|
||||||
|
Loading…
Reference in New Issue
Block a user