mirror of
https://gitlab.uni-freiburg.de/opensourcevdi/spice
synced 2025-12-26 06:32:44 +00:00
Just to not forget some steps Signed-off-by: Frediano Ziglio <fziglio@redhat.com> Acked-by: Victor Toso <victortoso@redhat.com>
1.6 KiB
1.6 KiB
How to do a SPICE server release
Some notes to prepare a release, not really strict but better to have in order to avoid forgetting something.
- Update
configure.acandmeson.buildaccording to libtool rules - Update
CHANGELOG.mdwith list of changes done since last release - Send a merge request with such changes, handle the review
- Try to build an RPM package from
make distoutput (see below notes on how to build a source tarball) git pushfor the above MRgit pushfor the version tag created (for instance you can usegit push origin v0.14.3orgit push --tags)- Send an email to spice-devel mailing list
- Sign generated tarball (to create a detached signature run
gpg2 -sb spice-release.tar.bz2) - On Gitlab update tags (https://gitlab.freedesktop.org/spice/spice/-/tags)
- Add ChangeLog information
- Upload tarball and relative signature
- Upload tarball and relative signature to
https://www.spice-space.org/download/releases/ (sftp to
spice-uploader@spice-web.osci.io:/var/www/www.spice-space.org/) - Update file
download.rstin https://gitlab.freedesktop.org/spice/spice-space-pages - Create a merge request for
spice-space-pages
How to build a source tarball
git tag -a v0.14.3 -m 'spice-server 0.14.3'(replace the version)git clone https://gitlab.freedesktop.org/spice/spice.gitcd spice./autogen.sh --disable-dependency-tracking(cd subprojects/spice-common && make gitignore)make dist
Step 4 is to avoid a problem with .deps directories, step 5 to avoid
the directory to be dirty due to missing .gitignore files.