Xfce Wiki

Sub domains
 

This is an old revision of the document!

Xfce Release How To

Please seehttps:docs.xfce.org/contribute/dev/start for an up to date documentation! </note> ===== 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). - 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 ===== - Run ./autogen.sh - Run make distcheck - Check auto generated files: INSTALL, COPYING - If at this stage everything works, run git commit -m 'Updates for release' - Now you are ready to tag the current master:
<code>git tag -a <package>-<version> # e.g. xfce4-power-manager-1.3.2 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 git-tag manual. - Now you can release the package using the xfce release manager. Folow the instructions on that site. ===== Post-release ===== - Edit configure.in.in or configure.ac.in. - Reset <package>_version_tag to git. - Commit (git commit -m “Back to development”) and push. - Add the version to the bugzilla component.