| Version 1.9 Build 1488
|
|
Next: Glish
Up: AIPS++ DEVELOPMENT PLAN: Release 1.4
Previous: Applications integration
Subsections
This covers all system work, excluding maintenance and support of the
basic library.
- Stability
- A fundamental requirement in this cycle is the
continued provision of a stable build to maximize application
development and testing efficiency. The project is now operational and
build failures have a significant impact on applications development
efficiency and the ease of user support.
- End-user release support
- With the project in an operational
phase, the provision of end-user installation and release update
support is a high priority. This includes a mechanism for assembling
release patches automatically.
- Initial developer support
- An initial group of external
developers is starting to use the system for exploratory
development. This group can be supported in the most cost-effective
manner by starting to provide formal support for external development
on very restricted platforms in advance of the full developer's
release, which is planned for 2001.
- Finish changelog implementation
- Complete the implementation of
the current changelog system. (GvD, H, 1 wk).
- Prepare initial developer's release
- Document the makedefs, and
provide an installation FAQ for an initial developer's release,
targeted at RedHat and SuSe Linux systems of restricted version
numbers. Test the resulting CDs. (GvD, H, 2 wk).
- Automated patch generation
- Complete a utility to automate patch
generation by tracking library dependencies. (DS, H, 2 wk).
- Implement global data proposal
- Implement the existing global
data proposal using CVSup. (DS, H, 2 wk).
Next: Glish
Up: AIPS++ DEVELOPMENT PLAN: Release 1.4
Previous: Applications integration
  Contents
Please send questions or comments about AIPS++ to aips2-request@nrao.edu.
Copyright © 1995-2000 Associated Universities Inc.,
Washington, D.C.
Return to AIPS++ Home Page
2006-08-01