Actions

Difference between revisions of "Release procedure and checklist"

From Joomla! Documentation

(Calculating Release Statistics)
(document jcode details)
Line 35: Line 35:
 
# If problems are found during this stage, go back to fix the problem. Use the [[Joomla! Maintenance Procedures]] and repeat until tests are performed successfully.
 
# If problems are found during this stage, go back to fix the problem. Use the [[Joomla! Maintenance Procedures]] and repeat until tests are performed successfully.
 
# Add package to joomlacode.org
 
# Add package to joomlacode.org
 +
## Before the release is public, set the joomlacode package flags as follows: Visible=No, Public=No, Require Login=Yes.
 +
## Set the Release flags as follows: Visible=Yes, Released=Yes.
 +
## Once package is released, change the Package flags to Visible=Yes, Public=Yes, Require Login=No.
 +
## Change the prior version package to Visible=No but leave the prior version release flags as they are.
 
# Publish announcement on joomla.org and the forum, change download module image and link
 
# Publish announcement on joomla.org and the forum, change download module image and link
 
# Make static copy of front page with announcement to be used if server load becomes critical.
 
# Make static copy of front page with announcement to be used if server load becomes critical.

Revision as of 09:17, 27 April 2010


There is a general checklist when a version of Joomla! is released. Keep in mind that a major release differs a lot from a Minor Release or even a Maintenance Release. The checklist here describes the steps that need to be done for (at least) Maintenance Release and Minor Release.

Contents

Release checklist

It depends on the Development Cycle when the checklist is triggered. A release can be done during every stage of the Development Cycle, it does not matter if you release a beta or a stable version, this is a general checklist that can be used when releasing a new version of Joomla! The checklist starts when it's decided to release a version:

Preparation phase

  1. Communication pre-release: check with all Working Group Coordinators for status
  2. Communication pre-release: check with Lead Developers for status
  3. Communication pre-release: inform Bug Squad and Development Team of upcoming release
  4. Decision: when the above has positive result, set a date and time for release
  5. Communication pre-release: inform Global Moderators about upcoming release
  6. Communication pre-release: check availability and assign release tasks to Core and work-group members.
  7. Close trunk on predefined date and time (Development Coordinator, also sends an e-mail to development list).
  8. Image for front page download module, has to be modified for the release.
  9. Contact foundation work group for creation of Front page announcement.
  10. Determine release name

Pre-execution phase

  1. Apply latest translations (need to be delivered by translation work group).
  2. Create test package.
  3. Offer test package to testers: Bug Squad members, Development Team members, translation members
  4. If problems are found during this stage, go back to fix the problem. Use the Joomla! Maintenance Procedures and repeat until tests are performed successfully.

Execution phase

  1. Change version information.
  2. Enable install check.
  3. Add entry in CHANGELOG.php file
  4. Package build.
  5. Offer test package to testers: Bug Squad members, Development Team members, translation members
  6. If problems are found during this stage, go back to fix the problem. Use the Joomla! Maintenance Procedures and repeat until tests are performed successfully.
  7. Add package to joomlacode.org
    1. Before the release is public, set the joomlacode package flags as follows: Visible=No, Public=No, Require Login=Yes.
    2. Set the Release flags as follows: Visible=Yes, Released=Yes.
    3. Once package is released, change the Package flags to Visible=Yes, Public=Yes, Require Login=No.
    4. Change the prior version package to Visible=No but leave the prior version release flags as they are.
  8. Publish announcement on joomla.org and the forum, change download module image and link
  9. Make static copy of front page with announcement to be used if server load becomes critical.

Finalization phase

  1. Tag SVN.
  2. Un-freeze the trunk, send e-mail to work groups and mailing lists (Development Team and Bug Squad).
  3. Undo install check.
  4. Change content on joomla.org and dev.joomla.org (see pages to update)
  5. Update MD5 checksum information
  6. Update nightly builds to reflect new release

Pages to update

  1. Global:
  2. 1.5:
    • Create new Wiki article called 'Category:Version 1.5.X FAQ'. Add an overall note for the release in the body of the article using the previous version as a Guide. Insert the following into the article: [[Category:Version 1.5 FAQ]]. Include a link to the 'Category:Version 1.5.x FAQ' page in the Release notes.
    • Update Version History
    • Update Joomla! Codenames
  3. 1.0:

Calculating Release Statistics

  1. Extract *all* issues from Tracker into spreadsheet. Make note of the date of the last release and the number of active issues at the time of the last release.
  2. Set a filter on the "Closed Date" column to be "after" "the day of the last release".
    • Calculate "Closed" count by aggregating status values for Closed, Duplicate Report, Known Issue, Not a bug, Not Joomla! Core, Unable to Confirm.
    • Calculate "Fixed in SVN" count by aggregating status values for Open and Information Required. (Note: this value is presented two times in the report.)
  3. Set a filter on the "Closed Date" column to be blanks:
    • Calculate "Open" count by aggregating status values for "Open" and "Information Required."
    • Calculate "Confirmed" count by aggregating status values for "Confirmed" and "In Progress."
    • Calculate "Pending" count by aggregating status values for "Pending" and "Ready to Commit."
  4. Calculate the "New Active Issues" by aggregating the "Open", "Confirmed" and "Pending" counts.
  5. Calculate the "net increase/decrease" by subtracting the "Last Release Active Issues" from the "New Active Issues."
  6. Count the "number of commits" by reviewing the CHANGELOG.php file and counting the documented commits.

Alternative Method for Stats

  • Fixed in SVN: Create query with close date > date of prior release and status = Fixed in SVN.
  • Commits: Count from CHANGELOG.php as indicated above.
  • New Reports: Run query with all status codes and open date > date of prior release.
  • Increase / decrease in active issues: See note below
  • Closed: Run query with closed date > date of prior release and status code one of Closed, Duplicate Report, Known Issue, Not a bug, Not Joomla! Core, Unable to Confirm.
  • Open at time of release: query of all issues with status = Open or Information Required
  • Confirmed at time of release: query of all issues with status = Confirmed or In Progress
  • Pending at time of release: query of all issues with status = Pending or Ready to Commit

Increase/Decrease in Active Issues

  • Total active issues now = Open at time of release + Confirmed at time of release + Pending at time of release
  • This number minus the total active as of prior release is the net increase or decrease

As a check, make sure the following formula works:

  • Prior release total active issues + New Reports - (Closed + Fixed in SVN) should equal the Total Active Issues now.