Release Checklist

From Octave
Revision as of 16:11, 1 February 2015 by Rik (talk | contribs) (Rik moved page Roadmap to Release Checklist: General release checklist to complete before each release)
Jump to navigation Jump to search

GUI Release Tasks

This page shows the tasks to be completed before the GUI release is finalized.

  1. File bug reports for all outstanding bugs known, but not reported
    • Put out a general call for reports on Octave-Maintainers and Octave-Help list
    Completion Date:
  2. Review patch tracker/bug list for any patches submitted that may be included before release
    Completion Date:
  3. Identify Bugs which *must* be fixed prior to release
    • Review bugs on tracker for possible inclusion in list
    • Review bugs and update to correct category, such as Patch submitted
    Completion Date:
  4. Clear all bugs identified as must-fix
    Completion Date:
  5. GPL License activities
    • Update Copyright statements for all source controlled files
    • Add any new contributors to
    Completion Date:
  6. Style-check code base
    • This will produce lots of whitespace changes, but no behavior changes
    • Must occur after patches have been added since whitespace changes will often prevent patches from applying
    Completion Date:
  7. Run lint checker on code base
    • cppcheck, Clang sanitize, etc.
    Completion Date:
  8. Verify 'make check' is passing
    • Start discussion on octave-maintainers list about which failing tests must be fixed
    • Identify and fix any tests determined critical in step above
    Completion Date:
  9. Run Octave test suite under Valgrind to check for memory leaks
    Completion Date:
  10. Review documentation
    • Grammar check documentation so that it conforms to Octave standards
    • Spell check documentation
    • Verify no functions missing from manual
    • Verify deprecated functions removed from "see also" links
    • Verify all formats (Info, HTML, pdf) build correctly
    • Review NEWS for any features which should be announced
    Completion Date:
  11. Localization and Internationalization
    • Submit call for translations for GUI strings.
    Completion Date:
  12. Verify build process and create release candidates
    • Update version information in
    • Verify 'make distcheck' passes
    • Create release candidate
      • 'make dist'
      • hg tag repository with release candidate ID
      • For Windows, create installer Windows Installer
      • Upload release candidate
      • Announce release candidate to Octave-Maintainers, Octave-Help, on web page
      • Repeat release candidate cycle until clean
    Completion Date:
  13. Final Release
    • hg tag repository with release
    • merge default onto stable to become the current stable release
    • add new release version to Savannah bug tracker
    • Announce final release on Octave mailing lists and web site
    Completion Date:
  14. Post-Release
    • Update versioning to next release cycle
    • Remove all deprecated functions scheduled for deletion in default branch
    Completion Date:

Current version policy

According to the discussions on the mailing list (, a rough roadmap has been sketched for the development:

  1. New experimental features and development go into the default branch.
  2. The current Merging order goes like this: stable -> gui-release -> default

The rules for what goes on each branch are roughly

  1. Critical non-GUI fixes found in the stable release go on stable and get forward-merged into release-gui and default. We know the GUI is full of bugs, which is the point of the release-gui branch, so all GUI fixes go into gui-release. Fixes that break API go into default.

    But note that since we are not installing any of the headers from the libgui directory, there are few (if any) changes that we could make to the GUI that could considered to break the API. So pretty much any change to the GUI is allowed as long as it only touches files in the libgui directory. But of course we are expecting that changes to the GUI improve stability and remove bugs, not the opposite, so let's not go too wild with redesigning and refactoring. We can think about those things after 4.0.

  2. Everything else is shades of grey, but I recommend for starters: fixes that change non-GUI behavior or API go into default. Simple fixes can go into gui-release, more complex changes into default. The shades of grey are deciding what "simple" and "complex" mean, but we can judge these on a case-by-case basis.