CASA 3.2 Release Status and Process

Page Status: Complete - CASA 3.2.0 released on 2011-05-13.

Here is a summary what has been happening on the CASA 3.2.0 release so far, and what we plan for the remainder of the release. Some of this is a continuation of existing processes. Some of this has changed for this release.

This page describes the current process, not the ideal process. We will discuss improvements to this process after we complete the 3.2.0 release based on experience with this release.

Status

2011-05-13 : Released

2011-04-25 : Test Status

For source code versions:

Summary:

  OS X 10.5 OS X 10.6 RHEL 5.5
  32 bit 64 bit 32 bit 64 bit
regression.py tests tbd all but 2 pass all but 2 pass all but 2 pass
runUnitTest.py tests tbd 740 tests run with 1 errors, 0 failure tbd all 740 tests pass

Error Tests:

  OS X 10.5 OS X 10.6 RHEL 5.5
  32 bit 64 bit 32 bit 64 bit
test_simplecluster tbd fail tbd pass

  • test_simplecluster: not expected to run on OS X. Test to be improved later.

Failing Tests:

  OS X 10.5 OS X 10.6 RHEL 5.5
  32 bit 64 bit 32 bit 64 bit
ngc4826_regression tbd fail fail fail
ngc4826c_regression tbd fail fail fail

  • ngc4826_regression: the responsible developer has been contacted. He is busy with other work.
  • ngc4826s_regression: the responsible developer has been contacted. He is busy with other work.

2011-04-11 : On 2011-04-08, I created a stable/casa-3.2.0-2 branch from test. This included:

  • test r14639
  • asap r2128
  • pyrap r326

If you have changes that belong in the 3.2.0 release that you have already checked in to active, please send the change numbers to me and I will merge them into the test and stable/casa-3.2.0-2 branches as soon as possible.

If you have changes that belong in the 3.2.0 release that you have not yet checked in, please check out stable/casa-3.2.0-2 and check in your changes there. I will merge these changes back to active daily.

Test reports from ESO

Please see this page

Process

Feature Freeze

The CASA 3.2.0 release feature freeze was discussed in CASA staff meetings, with a planned date of 2011-03-15. There was no formal announcement when the freeze went into effect. The active branch did not contain all code for all features planned for CASA 3.2.0 until 2011-03-25. Bug fixes for those features continue to arrive on active.

"active" Branch

This process was in place before the start of the CASA 3.2.0 release process. It will remain in place after we complete this release.

Builds

Automated builds run on each check in to Subversion. The developer who checked in a change is notified of any failures.

Status is available at http://warp.cv.nrao.edu:8080/

Tests

On a successful automated build, python/2.6/runUnitTest.py is run to execute a subset of tool and task tests. The developer who checked in a change is notified of any failures.

Status is available at http://warp.cv.nrao.edu:8080/

Bug Fixes

Bug fixes to issues found on the active branch must be checked in to the active branch.

"test" Branch

Builds

Changes from active marked "Ready for Test" are manually merged to the test branch periodically (at this time, daily). Changes are built manually. If the changes fail to build, additional code is selectively merged in from active until code builds. If this is not sufficient, developers are asked to help resolve build issues.

Tests

On a successful manual build, we manually run linux_64b/python/2.6/regression.py to execute a subset of regression tests. On a "good enough" (not well defined) regression test run, we update code/VERSION with the current date and time, and check in merged code to the test branch. This triggers an automated build and full regression test run on a set of servers in CV. Developers are notified of regression test failures. The product of the automated build is copied to (TBD), where other automated systems may pick up the build and install it for user testing.

Bug Fixes

Bug fixes to issues found on the test branch must be checked in to the active branch. They will be merged back to the test branch as part of routine test branch updates.

"stable" Branch

Builds

Once test failures on the test branch have been reduced to a manageable level, we will create a new stable/casa-3.2.0-X branch. This will include all changes on the test branch at the time.

Once this branch is created and confirmed to build correctly, it will be copied to stable/current. This triggers an automated build and test run on a set of servers in CV. Developers are notified of test failures. The product of the automated build is copied to (TBD), where other automated systems may pick up the build and install it for user testing.

Tests

TBD

Bug Fixes

Bug fixes to issues found on the stable branch must be checked in to the stable branch. Only bug fixes to bugs found on the stable branch may be checked in to the stable branch.

I will manually build and test bug fixes to the stable branch. If they succeed, the branch will be copied to stable/current. This will trigger the automated build and test described above.

I will merge bug fixes from the stable branch to the active branch periodically (TBD).

"release" Branch

Builds

Once the stable branch has been sufficiently tested (not well defined), we will create a new release/casa-3.2.0 branch. This will include all changes on the stable/casa-3.2.0-X branch at the time.

Once this branch is created and confirmed to build correctly, it will be copied to stable/current. This will trigger automated builds and tests on a set of servers in CV. Developers are notified of test failures. The product of the automated build is copied to (TBD), where other automated systems may pick up the build and install it for user testing.

Tests

TBD

Bug Fixes

Bug fixes to issues found on the release branch must be checked in to the release branch. Only bug fixes to bugs found on the release branch may be checked in to the release branch.

I will manually build and test bug fixes to the release branch. If they succeed, the branch will be copied to release/current. This will trigger the automated build and test described above.

I will merge bug fixes from the release branch to the active branch periodically (TBD).

-- ScottRankin - 2011-03-31

This topic: Software > TWikiUsers > ScottRankin > Casa32Release
Topic revision: 2011-06-22, ScottRankin
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding NRAO Public Wiki? Send feedback