Last updated by Scott Rankin on 05-13 per instructions from Mark Rawlings.
Last reviewed by Mark Rawlings on 05-12.
on EL5, EL6 and OS X 10.7. See
"push on getting a user-testable RHEL package done ASAP, and take the subsequent hit on the OS X delivery time." - Mark via e-mail, 05-13.
Prepare for my orderly departure from NRAO. See
JIRA tickets, in priority order.
Wipe and reinstall 10.7 on cbt-d11-1, reconfigure for 10.7 CASA development.
pending plan for allocating OS X development and test systems in DSOC.
OS X 10.7. See
Configure an OS X 10.7 development system for Susan Loveland. See
Ready for Susan.
Publish CASA 4.2.1 EL5 and EL6 only, internally to CASA.
Publish CASA Linux test packages from CASA 4.3 trunk. See
Build and test CASA trunk on EL6. See
Collect OS X 10.7 test & debugging data for CASA 4.2.1
Re run failing tests with only an ssh connection - to see if others can test and debug without a dedicated Mac.
Collect 10.8 and 10.9 data where possible.
Re run failing tests on Linux to see if they can be debugged there.
data recorded in JIRA.
on EL5, EL6. See
Complete update of 3rd party packages on OS X. See
Update OS X packaging scripts for changes to CASA 3rd party packages. See
From 2011-2014 PEPs, reorganized for easier measurement, and listed in priority order based on recent instructions from management.
Deliver CASA packages to users.
Deploy CASA packages to all NRAO sites.
Publish CASA packages for use outside of NRAO.
Coordinate deployment of CASA packages with NRAO Helpdesk.
Build and Acceptance Test CASA packages for
This includes pre-package build and post-package build testing to isolate the source of issues found in packages.
Create and monitor change control branches required to build CASA packages, particularly releases.
Merge CASA code between change control branches to ensure correct CASA features are included in release packages.
Help CASA developers use change control to minimize the cost of delivering CASA.
Monitor CASA automated build and test systems.
Assist developers in resolving CASA issues exposed by automated build and test.
Extend automated build and test systems to improve CASA test coverage.
Deliver 3rd party packages required by CASA developers.
Ensure CASA can deliver correct, reproducible 3rd party packages to all CASA developers on all CASA supported Linux distributions and OS X versions.
Document procedures for setting up CASA development computers.
Ensure source code used to build CASA 3rd party packages is kept in CASA change control.
Coordinate deployment of CASA 3rd party packages with NRAO helpdesk.
Working with NRAO Helpdesk, deploy CASA 3rd party packages to CASA developers at all NRAO sites.
Publish CASA 3rd party packages for use by CASA developers outside of NRAO.
Improve CASA build and tests automation.
Investigate issues reported by CASA users for OS related issues, resolve where possible.
Organize and maintain the CASA Software Engineering Wiki.
Coordinate or lead several Software Engineering projects listed on the CASA Software Engineering Wiki.
Provide assistance to CASA developers on the topics of
Software Change Control
Software Delivery (deployment within NRAO and publishing outside of NRAO)
General Software Development
General Software Engineering
Applying Ideas From The Book "Continuous Delivery" to CASA
Rewrite CASA Software Engineering Page
ESO public wiki
NRAO internal wiki
Employee Self Services (ESS and ETK)
SSH Tunneling Web Browsing
CASA Software Engineering
Daily "regression" test
old build/test notes
Old CASA Build Notes
Create project pages for:
Describe an idealized CASA build and test system - start from
Describe an idealized approach to CASA testing - start from
CASA Testing Improvmements
Standardize CASA Package Contents - start from
CASA Packaging Requirements
Write notes for new CASA developers - start with
CASA Development Infrastructure Links
Notes for New CASA Developers
Document CASA development dependencies - start with
Document how CASA data moves from casa-data/trunk to rest of system - start with
Document how to package CASA - start with:
Notes, not ready to share: |
CASA Test Noise
CASA Python Coding Standards
Charlottesville Trip 2012-07
Software Version Numbers
I no longer work on ALMA. The links below are not maintained.
Issue Tracking (Jira)
ALMA Software Subsystems:
IDL Simulator Extensions 2
Archive Verification Procedure
ITS work 2010 Fall
Naming Conventions for Branches
ALMA Software Function Based Teams:
Wiki - phase 1
Wiki - phase 2
ALMA Test Systems:
Eclipse as used in ALMA:
Eclipse Support to Code Inspections
2010 PEP Projects:
Complete Array Status GUI - OMC plugin due in Chile 2010-12-01, Web monitor due 2010-04-01
Extend Antenna Status GUI - due 2010-04-01
Add Front End
New ACD Hardware Device GUI - due 2010-04-01
New WVR Hardware Device GUI - due 2010-04-01
2009 PEP Projects:
Complete work on RTOS FBT
- Done 2009-07-31
Create PSCR Device
- Tested in STE on ALMA-6_1_1-B 2009-08-19
ALMA CONTROL Device GUIs
Setup AOC STE 3
- view a short introductory presentation on TWiki for beginners
- starting points on TWiki
- complete TWiki documentation, Quick Start to Reference
- try out TWiki on your own
- just for me
Uncomment preferences variables to activate them (remove the #-sign). Help and details on preferences variables are available in
Show tool-tip topic info on mouse-over of
links, on or off:
#Set LINKTOOLTIPINFO = off
Horizontal size of text edit box:
#Set EDITBOXWIDTH = 70
Vertical size of text edit box:
#Set EDITBOXHEIGHT = 22
Style of text edit box.
for full window width (default),
#Set EDITBOXSTYLE = width: 99%
Write protect your home page: (set it to your
#Set ALLOWTOPICCHANGE =
for changing your password
for changing your email address
has a list of other TWiki users
is a list of TWiki user documentation
lists all TWiki user tools
This topic: Main
Copyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding NRAO Public Wiki?