Developer Infos

From Netatalk Wiki
Jump to: navigation, search
(Basic Netatalk Git)
(Making a release)
Line 148: Line 148:
  
 
Developers doing releases are expected to have a working understanding of the ABI checking infrastructure and must use the --enable-developer configure option.
 
Developers doing releases are expected to have a working understanding of the ABI checking infrastructure and must use the --enable-developer configure option.
 
* Create release branch from "develop" branch
 
  $ git checkout -b release-3.0beta2
 
  Switched to a new branch 'release-3.0beta2'
 
  
 
* Bump VERSION
 
* Bump VERSION
Line 204: Line 200:
  
 
* Run make distcheck, fix any errors
 
* Run make distcheck, fix any errors
No errors? Great, time to release:
 
  
* Switch to 3.0 release branch "master"
+
* Update manpages
   $ git checkout master
+
   $ make html
   $ git merge release-3.0beta2
+
   $ git commit -a -m "Generate manpages from XML"
   ...
+
 
   $ git push SOURCEFORGE-GIT-REPO master
+
* Update and upload release notes:
 +
   $ cd doc/
 +
   doc/ $ vi www/ReleaseNotes
 +
  doc/ $ git commit -a -m "Update release notes"
 +
  doc/ $ USER=netatalk-sourceforge-adminuser make upload-release-notes
 +
 
 +
* Tag, release and roll tarballs
 
   $ git tag TAG
 
   $ git tag TAG
 
   $ git push SOURCEFORGE-GIT-REPO TAG
 
   $ git push SOURCEFORGE-GIT-REPO TAG
Line 216: Line 217:
 
   $ make dist-bzip2
 
   $ make dist-bzip2
  
* Merge changes from release branch back into develop
+
* Upload updates online manual:
   $ git checkout develop
+
   $ cd doc/manual/
   $ git merge release-3.0beta2
+
   $ USER=netatalk-sourceforge-adminuser make html-upload
  $ git branch -d release-3.0beta2
+
  
 
* Reset VERSION to eg 3.0dev
 
* Reset VERSION to eg 3.0dev

Revision as of 07:47, 15 February 2014

Personal tools
Namespaces
Variants
Actions
Navigation
Toolbox