Getting Started

Documentation

Glish

Learn More

Programming

Contact Us

Version 1.9 Build 803

News	FAQ
Search	Home

Introduction

The purpose of this document is to outline the deliverables in the forthcoming release of version 1.3. This updates the previous development plan..

The immediate priorities for the AIPS++ project are:

• Maintain and support the released package,
• Establish a high level of responsiveness to user feedback,
• Establish 6-month plan-develop-test-release cycle.
• Implement and executes a systematic approach to the internal testing of the released package,
• Complete another phase of integration of the applications
• Establish completeness in various key applications areas

Release 1.2 is now going out the door. It has a stable Glish, a reasonable GUI, lots of synthesis imaging, a thin-path for calibration, a version of the single dish analysis program dish, extensive image analysis capability, two versatile display programs, and lots of miscellaneous functionality. The documentation framework is now all in place but the documentation itself must be filled out.

We intend to settle down on a 6 month plan-develop-test-release (PDTR) cycle. The time scale is as follows, counting from the date of the previous major release.

+0 weeks

Revise planning documents

+2 weeks

Finalize planning, assign targets

+2 weeks

Start development, testing

+2 weeks

Initiate completion of testing of existing capabilities

+4 months

Freeze new checkins, start dedicated testing

+5 months

Hard freeze, uprev to next versions of release and develop masters.

+5.5 months

Cut final CDs

+6 months

Ship CDs

The times required for each step may vary but we intend to stick to this regular major release schedule. Note that patches to the previous release will be issued as needed, probably on a 4-6 week interval.

In the medium term (end of 2000), we expect that the third release (probably 1.4) will have most of the synthesis calibration and imaging tools present for all consortium telescopes. Following that we will next target a developer's release.

We must act with discipline in setting and acheiving targets. In particular, at this point in the cycle, we must not schedule too much to be completed before the freeze. Accordingly, I have changed some of the submitted plans to defer some work until the next release.