You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc/sphinx-guides/source/developers/making-releases.rst
+17-8Lines changed: 17 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -284,13 +284,22 @@ The build number will appear in ``/api/info/version`` (along with the commit men
284
284
Build Installer (dvinstall.zip)
285
285
-------------------------------
286
286
287
-
- In a git checkout of the dataverse source switch to the master branch and pull the latest.
288
-
- Copy the war file from the previous step to the ``target`` directory in the root of the repo (create it, if necessary):
289
-
- ``mkdir target``
290
-
- ``cp /tmp/dataverse-6.10.1.war target``
291
-
- ``cd scripts/installer``
292
-
- ``make clean``
293
-
- ``make``
287
+
In a git checkout of the source, switch to the master branch and pull the latest.
288
+
289
+
Copy the war file from the previous step (shown in ``/tmp`` in the example below ) to the ``target`` directory in the root of the repo (create the ``target`` directory, if necessary):
290
+
291
+
.. code-block:: bash
292
+
293
+
mkdir target
294
+
cp /tmp/dataverse-6.10.1.war target
295
+
296
+
Then, create the installer:
297
+
298
+
.. code-block:: bash
299
+
300
+
cd scripts/installer
301
+
make clean
302
+
make
294
303
295
304
A zip file called ``dvinstall.zip`` should be produced.
296
305
@@ -299,7 +308,7 @@ Create a Draft Release on GitHub
299
308
300
309
Go to https://github.com/IQSS/dataverse/releases/new to start creating a draft release.
301
310
302
-
- Under "Select tag" you will be creating a new tag. Have it start with a "v" such as ``v6.10.1``. Click "Create new tag". Don't worry, this won't happen until you publish.
311
+
- Under "Select tag" you will be creating a new tag. Have it start with a "v" such as ``v6.10.1``. Click "Create new tag". Don't worry, the tag won't be created until you publish.
303
312
- Under "Target", choose "master". This commit will appear in ``/api/info/version`` from a running installation.
304
313
- Under "Release title" use the same name as the tag such as ``v6.10.1``.
305
314
- In the description, copy and paste the content from the release notes .md file created in the "Write Release Notes" steps above.
0 commit comments