Skip to content

Commit 61b9d47

Browse files
rob-mongodbjdestefano-mongo
authored andcommitted
Updates to version bumping. (#10)
1 parent 62a0eda commit 61b9d47

File tree

1 file changed

+18
-5
lines changed

1 file changed

+18
-5
lines changed

source/tutorials/version-bumping.txt

Lines changed: 18 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -36,9 +36,13 @@ been removed, and users should be redirected to ``reference/mongosqld``.
3636
Step 1: Branch
3737
~~~~~~~~~~~~~~
3838

39+
From the project's repository, create a new branch for the current
40+
version:
41+
3942
.. code-block:: sh
4043

41-
git checkout -b v2.2
44+
git checkout -b v2.2 upstream/master
45+
git pull --rebase
4246
git push origin v2.2
4347
git checkout master
4448

@@ -59,10 +63,19 @@ will find a file called ``build_conf.yaml``. Update this file's
5963
Step 3: Update published branches configuration
6064
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
6165

62-
In the ``docs-tools`` repository under the ``data/`` directory, you will
63-
find a file called ``bi-connector-published-branches.yaml``. Update this
64-
file to include a ``2.3`` version and a ``v2.2`` branch; and set the
65-
``version.upcoming`` key to ``2.3``.
66+
a. Create a new local branch in the ``docs-tools`` repository:
67+
68+
.. code-block:: sh
69+
70+
git checkout -B bi-v2.3 upstream/master
71+
git pull --rebase
72+
73+
b. Navigate to the ``data/`` directory and open the file named
74+
``bi-connector-published-branches.yaml``.
75+
c. Update this file to include a ``2.3`` version and a ``v2.2`` branch; and set the
76+
``version.upcoming`` key to ``2.3``.
77+
d. Commit your change and push the commit to origin <local branch>.
78+
e. Create a separate PR to merge the change to master.
6679

6780
.. list-table::
6881
:header-rows: 1

0 commit comments

Comments
 (0)