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:

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:

# 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.

+

# Update developer.joomla.org

+

## Create a new release notes menu item. There is a release notes menu and you can copy the menu item for the previous release there and modify appropriately.

+

### 2.5 - Just fill in the options with the tracker item #'s, which you can get from the GitHub commit log

+

### 3.x - Enter the dates for the release period and exclude 2.5 specific items

+

## Add Bug Squad Contributors module to the newly created release notes page. Copy the module for the previous release and change the dates and menu assignments for the new module. This produces the list of active Bug Squad members for a release period.

# 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.

+

## Before the release is public, set the JoomlaCode package flags as follows: Visible=No, Public=No, Require Login=Yes.

#* 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: <nowiki>[[Category:Version 1.5 FAQ]]</nowiki>. Include a link to the 'Category:Version 1.5.x FAQ' page in the Release notes.

#** Before updating, verify the cron jobs (JoomlaCode tracker sync and language updater) do not break with the update

+

#* [http://help.joomla.org Help Site (old)]

+

#* [http://api.joomla.org API Site]

+

#** Regenerate API docs for the new release

+

=== Calculating Release Statistics ===

+

==== Using JoomlaCode and CHANGELOG ====

# 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.

# 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.

# Set a filter on the "Closed Date" column to be "after" "the day of the last release".

# Set a filter on the "Closed Date" column to be "after" "the day of the last release".

Line 87:

Line 121:

# Count the "number of commits" by reviewing the CHANGELOG.php file and counting the documented commits.

# Count the "number of commits" by reviewing the CHANGELOG.php file and counting the documented commits.

−

===Alternative Method for Stats===

+

==== Using GitHub ====

+

# Go to https://github.com/joomla/joomla-cms/compare/<version>...master where <version> is the previous release, this is GitHub's comparison view and will give stats from the previous release tag to the currently published master

+

# From this page, you can compile the number of commits, contributors, and files changed during the release period

+

+

==== Download Statistics ====

+

# Go to http://joomlacode.org/gf/project/joomla/frs/?action=FrsReport

+

# In the filter bar, set the start date to the date of the previous release and the end date to the day before the new release

+

# The "Downloads By Package" chart is the total number of downloads for each release (i.e. 2.5.16 and 3.2.0) and includes an "Other" piece for all older version downloads

+

# The "Downloads By Release" chart separates the packages by new install and updates

+

+

==== Alternative Method for Stats ====

* Fixed in SVN: Create query with close date > date of prior release and status = Fixed in SVN.

* 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.

* Commits: Count from CHANGELOG.php as indicated above.

Line 97:

Line 141:

* Pending at time of release: query of all issues with status = Pending or Ready to Commit

* Pending at time of release: query of all issues with status = Pending or Ready to Commit

−

====Increase/Decrease in Active Issues====

+

==== Increase/Decrease in Active Issues ====

* Total active issues now = Open at time of release + Confirmed at time of release + Pending at time of release

* 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

* This number minus the total active as of prior release is the net increase or decrease

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

Communication pre-release: check with PLT on timing

Communication pre-release: inform Bug Squad and LT's about timing

Decision: when the above has positive result, set a date and time for release

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.

Update developer.joomla.org

Create a new release notes menu item. There is a release notes menu and you can copy the menu item for the previous release there and modify appropriately.

2.5 - Just fill in the options with the tracker item #'s, which you can get from the GitHub commit log

3.x - Enter the dates for the release period and exclude 2.5 specific items

Add Bug Squad Contributors module to the newly created release notes page. Copy the module for the previous release and change the dates and menu assignments for the new module. This produces the list of active Bug Squad members for a release period.

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.

Update XML file on site for the new version number information.

FTP connect to update1.joomla.org and Navigate to www/core

All releases

Change version attribute in list.xml (don't add new line except when incrementing major/minor version numbers)

LTS Release

Change the update elements for the series with the new version number and new downloadurl and link to new archive file to extension.xml

STS Release

Navigate to www/core/sts

Change version attribute in list_sts.xml (don't add new line except when incrementing major/minor version numbers)

Change the update elements for the series with the new version number and new downloadurl and link to new archive file to extension_sts.xml

Test auto update from prior version(s) (make sure XML files have been copied to the SDN on update.joomla.org first)

All releases

Navigate to www/core/test

Change version attribute in list_test.xml (don't add new line except when incrementing major/minor version numbers)

LTS

Upload patch package to this folder

Change the update elements for the series with the new version number and new downloadurl and link to new archive file to extension_test.xml

STS

Navigate to www/core/teststs

Upload patch package to this folder

Change the update elements for the series with the new version number and new downloadurl and link to new archive file to extension_sts.xml

Calculate "Pending" count by aggregating status values for "Pending" and "Ready to Commit."

Calculate the "New Active Issues" by aggregating the "Open", "Confirmed" and "Pending" counts.

Calculate the "net increase/decrease" by subtracting the "Last Release Active Issues" from the "New Active Issues."

Count the "number of commits" by reviewing the CHANGELOG.php file and counting the documented commits.

Using GitHub

Go to https://github.com/joomla/joomla-cms/compare/<version>...master where <version> is the previous release, this is GitHub's comparison view and will give stats from the previous release tag to the currently published master

From this page, you can compile the number of commits, contributors, and files changed during the release period