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
dev:howto:release [2008/04/05 00:29] – mikedev:howto:release [2019/04/07 16:04] (current) – skunnyk
Line 1: Line 1:
 ====== Xfce Release How To ====== ====== Xfce Release How To ======
-This how to is under development but it might help. 
-Feel free to contribute. 
  
-===== Files to edit before release ===== 
-  - Release information: ''ChangeLog'', ''NEWS'' 
-  - Common information: ''README'', ''AUTHORS'', ''THANKS'', ''TODO'' (when present) 
  
-===== Configure file autoconf ===== +<note important>Please see https://docs.xfce.org/contribute/dev/start for an up to date documentation! 
-  - Edit autoconf file ''configure.in.in'' or ''configure.ac.in'' which name you've chosen. +</note>
-  - Remove ''svn'' from ''package_version_tag''. +
-  - Check the build dependencies.+
  
 +===== Considerations before releasing =====
 +  * Are the translations up to date, are the translator aware of you going to release.
 +  * All patches are applied and all known critical bugs fixed.
 +  * Do you have the feeling: "Yes, this code ready to be released upon the world, everyone should be able to enjoy it"? ;)
  
 +===== Files to update before release =====
 +  - Release information: ''ChangeLog'', ''NEWS''.
 +  - Common information: ''README'', ''AUTHORS'', ''THANKS'', ''TODO'' (when present).
 +  - [[http://git.xfce.org/xfce/xfce4-power-manager/commit/?id=10e532b0c6462cfa61faa5ebeddec7b7e454bfe3|Sample Commit]]
  
 +===== Configure script =====
 +  - Edit the configure script template ''configure.in.in'' or ''configure.ac.in''.
 +  - Set the package version (''<package>_version_major'', ''<package>_version_minor'' and ''<package>_version_micro'') to the version you want to release.
 +  - Remove ''git'' from ''<package>_version_tag''.
 +  - Check the build dependencies.
  
 ===== Check release package ===== ===== Check release package =====
-  - Run ''./autogen.sh''.+  - Run ''./autogen.sh''
   - Run ''make distcheck''   - Run ''make distcheck''
   - Check auto generated files: ''INSTALL'', ''COPYING''   - Check auto generated files: ''INSTALL'', ''COPYING''
-  - If at this stage everything works, commit all changes for release to trunk. +  - If at this stage everything works, run ''git commit -m 'Updates for release''' 
-  - Now you are ready to tag the current trunk: \\ <code>svn copy https://svn.xfce.org/svn/goodies/package/trunk \ +  - Now you are ready to tag the current master: \\ <code>git tag -a <package>-<version> # e.g. xfce4-power-manager-1.3.2 
-         https://svn.xfce.org/svn/goodies/package/tags/<package-version></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. 
 +  - Now you can release the package using the [[https://releases.xfce.org|xfce release manager]]. Folow the instructions on that site.
  
 ===== Post-release ===== ===== Post-release =====
   - Edit ''configure.in.in'' or ''configure.ac.in''.   - Edit ''configure.in.in'' or ''configure.ac.in''.
-  - Change ''package_version_major'', ''package_version_minor'' and ''package_version_micro'' version to the new release. +  - Reset ''<package>_version_tag'' to ''git''. 
-  - Re-add ''svn'' to ''package_version_tag''. +  - Commit (''git commit -m "Back to development"'') and push. 
 +  - Add the version to the bugzilla component.