OProfile release checklist

The OProfile maintainer must give you admin privileges to put out a release.

  1. Create/update Release Notes for new release
  2. Check if sample data file format has changed (libop/op_sample_file.h) the since previous release. If so, bump OPD_VERSION (in libop/op_config.h) if it hasn't already been done.
  3. Change version to non-git and commit
  4. Run
    make dist
  5. Make a release (candidate) publicly available.
    1. With a browser, go to the OProfile website and click on the "SOURCEFORGE.NET" at the bottom left of the screen.  Sign in with your admin user ID.  Click on "Files" tab and then click the "Add Folder" button. Name the folder "oprofile-<release>". Start with uploading the Release Notes file you created in step 1, but first, make a copy of it and rename it to oprofile-<release>_readme. Now go into the folder you just created, click the "Add File" button to upload the release notes "readme" file. Now click "Add File" and upload the new oprofile-<release>.tar.gz file.
    2. For each successive release candidate (and, eventually, for the GA), upload your release tar ball the into the "oprofile-<release>" folder you created above. Put a copy of the tar ball from the previous release candidate into the "oldfiles" folder; then delete it from the folder it was in. If the Release Notes file has changed, delete the old one and upload the new one.
    3. Go to project download page on SourceForge and verify that the new release tar ball is listed there. It will take some time for the new release to be mirrored to all of the mirror sites. Once you can successfully download the tar ball from a SourceForge mirror, got to the next step.
    4. For release candidates, post a message to the oprofile-list with a URL to the download page for the release you just created and paste the Release Notes into the message. For GA release, continue to the "Close fixed bugs" step.
    5. Get testing feedback from the community.  Return to step 1 for each new release candidate (and, eventually, for the GA).

    The following steps are to be done once the decision is made to GA and you've iterated over the previous steps again for the GA release.

  6. Close fixed bugs
  7. Update freshmeat
  8. Run the command
    'git tag RELEASE_<v_r_m>';  e.g, 'git tag RELEASE_0_9_4'
  9. Update web page release-notes/, news, download, srcdoc/, doc/
  10. Sync website to oprofile-www git
  11. Send release email
  12. Change AM_INIT_AUTOMAKE in configure.in '<v.r.m>git' and commit