Xfce Wiki

Sub domains
 

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Next revisionBoth sides next revision
releng:individual-releases [2009/10/16 15:10] – jannisreleng:individual-releases [2010/11/04 14:27] – jannis
Line 1: Line 1:
-====== HOWTO: Individual Releases ======+====== How to Perform Individual Releases ======
  
 ===== Bugfix Releases ===== ===== Bugfix Releases =====
Line 8: Line 8:
  
 ==== Preparations ==== ==== Preparations ====
- +
   - Check out the stable branch with <code>git checkout --track -b xfce-4.6 remotes/origin/xfce-4.6</code>   - Check out the stable branch with <code>git checkout --track -b xfce-4.6 remotes/origin/xfce-4.6</code>
 +  - Synchronize the branch with the public repository (for translations and fixes committed by others): <code>git pull --rebase</code>
   - Make sure the application compiles and that <code>./autogen.sh --enable-gtk-doc ... && make distcheck</code> works; commit build fixes as needed   - Make sure the application compiles and that <code>./autogen.sh --enable-gtk-doc ... && make distcheck</code> works; commit build fixes as needed
   - Update the NEWS, AUTHORS, README, THANKS, HACKING etc. files   - Update the NEWS, AUTHORS, README, THANKS, HACKING etc. files
-  - Update the ChangeLog from git with <code>git log > ChangeLog</code>+  - **If your ChangeLog is not generated automatically**, update the ChangeLog from git with <code>git log > ChangeLog</code>
  
 ==== Bumping the Version and Generating the Release Tarball ==== ==== Bumping the Version and Generating the Release Tarball ====
Line 27: Line 28:
  
   - Commit all local changes with a commit subject like this: <code>Release 4.6.1!</code>   - Commit all local changes with a commit subject like this: <code>Release 4.6.1!</code>
-  - After the commit, create an annotated tag for the release with <code>git tag -a xfwm4-4.6.1</code>+  - After the commit, create an annotated tag for the release with <code>git tag -a xfwm4-4.6.1</code> You can also sign the tag with a GPG key by adding an additional parameter to the ''git tag'' command. For more information about tagging read the ''[[http://www.kernel.org/pub/software/scm/git/docs/git-tag.html|git-tag]]'' manual.
   - Push the release commit and the tag with <code>git push && git push --tags</code>   - Push the release commit and the tag with <code>git push && git push --tags</code>
- 
-You can sign tags with a GPG key by adding an additional parameter to the ''git tag'' command. For more information   about tagging read the ''[[http://www.kernel.org/pub/software/scm/git/docs/git-tag.html|git-tag]]'' manual. 
  
 ==== Uploading the Release Tarball and Sending Announcements ==== ==== Uploading the Release Tarball and Sending Announcements ====
Line 38: Line 37:
   - Click on ''Release New Version'' link next to your project (''xfwm4'' in this case)   - Click on ''Release New Version'' link next to your project (''xfwm4'' in this case)
   - Follow the instructions presented to you by the release manager software to upload the ''xfwm4-4.6.1.tar.bz2'' tarball with the SHA1 checksum you computed before   - Follow the instructions presented to you by the release manager software to upload the ''xfwm4-4.6.1.tar.bz2'' tarball with the SHA1 checksum you computed before
-    - For the announcements, please only pick mailing lists that make sense. Everything should be announced on ''announce@xfce.org'' and ''xfce@xfce.org''. Software affecting developers should be announced on ''xfce4-dev@xfce.org'' in addition, and so on.+    * For the announcements, please only pick mailing lists that make sense. Everything should be announced on ''announce@xfce.org'' and ''xfce@xfce.org''. Software affecting developers should be announced on ''xfce4-dev@xfce.org'' in addition, and so on.
  
 ==== After the Release ==== ==== After the Release ====
Line 48: Line 47:
     * Gnomefiles     * Gnomefiles
     * others     * others
 +  - Switch back to the development branch using <code>git checkout master</code>
   - Celebrate   - Celebrate
  
 ===== Development Releases ===== ===== Development Releases =====