summaryrefslogtreecommitdiff
path: root/RELEASE-HOWTO.md
diff options
context:
space:
mode:
authorMarcus Meissner <marcus@jet.franken.de>2019-01-01 18:12:13 +0100
committerMarcus Meissner <marcus@jet.franken.de>2019-01-01 18:12:13 +0100
commit1f4772db486fc5e929d414a2aa9c253a53c74f76 (patch)
treea3398ec1b3536ff438dfb9c01fc83daa635c19c3 /RELEASE-HOWTO.md
parent646b057f3e88c0de9e6526180a7cadff7c53d28f (diff)
downloadlibgphoto2-1f4772db486fc5e929d414a2aa9c253a53c74f76.tar.gz
oadded RELEASE HOWTO
Diffstat (limited to 'RELEASE-HOWTO.md')
-rw-r--r--RELEASE-HOWTO.md96
1 files changed, 94 insertions, 2 deletions
diff --git a/RELEASE-HOWTO.md b/RELEASE-HOWTO.md
index 02c1d3cc5..04ff9fdc0 100644
--- a/RELEASE-HOWTO.md
+++ b/RELEASE-HOWTO.md
@@ -34,12 +34,104 @@
## tag release
- bump version in configure.ac, NEWS
+ bump version in configure.ac, NEWS, commit and push.
make clean
make
sudo make install
-## build relase
+## build and sign release ŧarballs
make distcheck
+
+ this builds .gz and .bz2 tarballs currently.
+
+ GPG detach sign
+
+ gpg --detach-sign -a libgphoto2-2.5.22.tar.bz2
+ gpg --detach-sign -a libgphoto2-2.5.22.tar.gz
+
+ this will create .asc files alongside the tarballs.
+
+ Similar when doing the gphoto2 release.
+
+## tag git
+
+ git tag libgphoto2-2\_5\_22-release
+ git push --tags
+
+## create a README for sourceforge
+
+ paste the NEWS blob from this release into README for uploading
+
+## SF upload
+
+ Create a new folder below libgphoto2 with the release number in it (Add Folder)
+
+ Inside that "Add File" of the two tarballs, the two .asc files and the README.
+
+ After upload, select "Info" on the .tar.bz2 tarball, and "Select All" for the Default download.
+ This will make it point the "default download" link to this tarball.
+
+ If you are uploading gphoto2, do the same ... but do not select it for the default download.
+
+## Github tagging
+
+ https://github.com/gphoto/libgphoto2/releases
+
+ "Draft a new release"
+
+ Select the new release tag. Name is "2.5.22 release",
+ paste in the NEWS blob into the textfield.
+
+## Edit the website
+
+### index.php
+
+ Use a entry similar to the current ones. Drop older ones occasionaly.
+
+### news/index.php
+
+ Paste in the NEWS blob, htmlify with h2 - h3 and ul/li lists, same as the ones before
+
+### proj/libgphoto2/support.php
+
+ Adjust the date (LANG=C date).
+
+ Adjust the gphoto2 --version blob (LANG=C gphoto2 --version). Make sure you have the correct versions in there.
+
+ Replace the table with fresh output of:
+
+ /usr/lib64/libgphoto2/print-camera-list html
+
+### Upload via sftp
+
+ see upload.sh ... html tree starts below htdocs/ on the server.
+
+ Do not forget to "svn ci" the changes.
+
+### Verify website.
+
+ Check the pages render OK and no HTML error was introduced.
+
+## Announce to mailing list
+
+ Write a summary email to gphoto-user@lists.sourceforge.net, gphoto-devel@lists.sourceforge.net
+
+## Announce to freshcode.club
+
+ https://freshcode.club/, look for libgphoto2
+
+ Fill out the "New release" form. It is pretty straight forward. As text use the NEWS blob again.
+
+## Announce to twitter / facebook / etc.
+
+ e.g.:
+
+ I have just released libgphoto2 2.5.22 ( http://gphoto.org/news/ )
+ ... Fixed Canon EOS M and PowerShot SX capture, added Sony Alpha RX0
+ and RX100M5A, added Canon EOS R, and some bugfixes.
+
+## Make git ready for further development
+
+ Rev NEWS and configure.ac versions to 2.5.22.1 devel release.