doc/dev/release-process.rst: note new 'project' arguments

Support added to the release scripts (from ceph-build.git) to
work for ceph-iscsi, so 'project' must be passed to these scripts,
and will appear in the prerelease pathnames.  See also
https://github.com/ceph/ceph-build/pull/2243 and
https://github.com/ceph/ceph-container/pull/2210

Signed-off-by: Dan Mick <dan.mick@redhat.com>
This commit is contained in:
Dan Mick 2024-05-22 15:25:51 -07:00
parent 4124ef2960
commit 7e64c6386e

View File

@ -188,11 +188,11 @@ See `the Ceph Tracker wiki page that explains how to write the release notes <ht
.. prompt:: bash
sign-rpms octopus
sign-rpms ceph octopus
Example::
$ sign-rpms octopus
$ sign-rpms ceph octopus
Checking packages in: /opt/repos/ceph/octopus-15.2.17/centos/7
signing: /opt/repos/ceph/octopus-15.2.17/centos/7/SRPMS/ceph-release-1-1.el7.src.rpm
/opt/repos/ceph/octopus-15.2.17/centos/7/SRPMS/ceph-release-1-1.el7.src.rpm:
@ -206,12 +206,12 @@ See `the Ceph Tracker wiki page that explains how to write the release notes <ht
.. prompt:: bash $
sync-push octopus
sync-push ceph octopus
This leaves the packages in a password-protected prerelease area
at https://download.ceph.com/prerelease. Verify them from there.
When done and ready for release, mv the directories to the parent
directory (that is, "mv <whatever you're promoting> ..".
at https://download.ceph.com/prerelease/ceph. Verify them from there.
When done and ready for release, mv the directories to the release
directory (that is, "mv <whatever you're promoting> ../..".
5. Build Containers