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
contribute:dev:make-a-release [2018/01/03 18:48] – [Update version number] skunnykcontribute:dev:make-a-release [2020/06/24 23:45] – skunnyk
Line 1: Line 1:
 ====== Making a Release ====== ====== Making a Release ======
  
-Before you start with this, make sure you understand the [[http://www.xfce.org/about/releasemodel|release model]] all developers should follow for core components.+Before you start with this, make sure you understand the [[https://www.xfce.org/about/releasemodel|release model]] all developers should follow for core components.
  
 ===== Version Numbering ===== ===== Version Numbering =====
Line 11: Line 11:
 <file bash> <file bash>
 # get the stable branch # get the stable branch
-git checkout --track -b xfce-4.12 remotes/origin/xfce-4.12+git checkout --track -b xfce-4.14 remotes/origin/xfce-4.14
  
 # pull the latest changes # pull the latest changes
Line 17: Line 17:
 </file> </file>
  
-Now make sure all the bug fixes are committed and pushed to the remote repository. You can check this at [[http://git.xfce.org|git.xfce.org]] as well.+Now make sure all the bug fixes are committed and pushed to the remote repository. You can check this at [[http://gitlab.xfce.org|gitlab.xfce.org]] as well.
  
 For the version number the //micro// version is increased by 1. So 4.12.2 becomes 4.12.3. For the version number the //micro// version is increased by 1. So 4.12.2 becomes 4.12.3.
Line 23: Line 23:
 ==== Development releases ==== ==== Development releases ====
  
-Unstable releases are created from the master branch, which is in this period in feature-freeze. There we use an odd //minor// number. So the first development release is for example 4.11.0, then 4.11.1 etc.+Unstable releases are created from the master branch, which is in this period in feature-freeze. There we use an odd //minor// number. So the first development release is for example 4.15.0, then 4.15.1 etc.
  
 ===== Build the tarball ===== ===== Build the tarball =====
Line 31: Line 31:
 ==== Update NEWS ==== ==== Update NEWS ====
  
-Update the NEWS, AUTHORS, README, THANKS, HACKING etc. files to credits are given where due.+xfce4-dev-tools from version 4.15.0 contains helpers: //xfce-get-release-notes//, //xfce-get-translations//, //xfce-update-news// to help you to update NEWS and list all translators. 
 + 
 +More script can be available on https://github.com/ochosi/xfce-helpers
  
 ==== Update version number ==== ==== Update version number ====
 +
   - Edit the configure script template configure.ac.in.     - Edit the configure script template configure.ac.in.  
   - Set the package version (<package>_version_major, <package>_version_minor and <package>_version_micro) to the version you want to release.     - Set the package version (<package>_version_major, <package>_version_minor and <package>_version_micro) to the version you want to release.  
Line 39: Line 42:
   - Check the build dependencies.    - Check the build dependencies. 
  
-==== Update the ChangeLog ==== 
- 
-All core modules have a ''Makefile.am'' rule to generate the ''ChangeLog'' during //distcheck//. If this is not the case, add the rule to the Makefile.am file (see https://git.xfce.org/xfce/libxfce4ui/tree/Makefile.am#n20 for an example) 
 ==== Compile the code ==== ==== Compile the code ====
  
Line 53: Line 53:
 ===== Tag release ===== ===== Tag release =====
  
-If the tarball is build successfully, it is time to tag the release in GIT.+If the tarball is build successfully, it is time to tag the release in git.
  
 <file bash> <file bash>
Line 66: Line 66:
  
 # send tag to remote # send tag to remote
-git push --tags abc.x.y.z+git push --tags
 </file> </file>
  
-For more information read the [[http://git-scm.com/docs/git-tag|git tag manual]].+For more information read the [[https://git-scm.com/docs/git-tag|git tag manual]].
  
 ===== Upload the tarball ===== ===== Upload the tarball =====
Line 83: Line 83:
  
   - Add the ''git'' back to ?_version_tag() in the ''configure.am.in'' file, commit and push the change.   - Add the ''git'' back to ?_version_tag() in the ''configure.am.in'' file, commit and push the change.
-  - Don't forget to add the version to your project on [[https://bugzilla.xfce.org/]]. 
   - Possibly switch back to the ''master'' branch.   - Possibly switch back to the ''master'' branch.
-  - Add the version to the bugzilla component. 
   - Celebrate  8-).   - Celebrate  8-).