Guidelines: Release en

From Pandora FMS Wiki
Jump to: navigation, search

1 First checks

  • Be sure that at least one people are making independent tests from you.
  • Make your own tests, different from local development tests (a separated machine used for testing enviroments, p.e).
  • Check our logs and performance periodically.

2 General issues

  • Be sure that there is no pending bugs waiting you in the bug tracking system.
  • Remove all debug code
  • Check for encoding and file formats (Unix/Windows) (specially if that files are coming from different people using different plattform/software).
  • Check version headers.
  • Check build number.
  • Check version variables inside code.
  • Update README (ascii file) from it latests version.
  • Check existance of LICENCE file in all packages.
  • Check all headers for updated licences.
  • Recheck that your local code is the same that is in repository, this also include "contrib" or "secondary" files like config skeleton files, tools, installers, etc.
  • Recheck that everybody has commited it latest final code to SVN before make the final checklist.
  • Dont't change anything after "freeze" version (except for very BIG problems). And never after pass the final checklist.
  • Make at least a "blank" full instalation, using all steps.

3 Final Checklist

  • Check version headers, do you remember this ? ;)
  • Check build number.
  • Check version variables inside code.
  • Update README (ascii file) from it latests version.
  • Check existance of LICENCE file in all packages.
  • Check all headers for updated licences.
  • Create tarball file with this syntax
 packagename_version-minorversion.tar.gz
  • Delete SVN tree information:
 find . -name ".svn" | xargs rm -Rf
  • Upload release files to SourceForge site.
  • Update Freshmeat with new release number.
  • If the release is significant, consider press releases to relevant news sources
  • Review the main website pages to add any new features
  • Add a news item to the project web sites and forums.
  • Send an email to the user and developer lists.