Policy on handling post-submission changes.

NRAO Interactive Services Modification Request 1C108, November 2007

1. Introduction

After the Oct 2007 deadline there were several minor requests from Carl and Lori to change / rename / update information on various proposals. Each time they requested Open Sky to do the work.

2. Background

Per Carl - Policy on handling post-submission changes. I also had a request to change the time requirements (they had enter an amount that was about 18 times too much - just a typo; on another occasion the PI needed to add a source they forgot, etc). I think policies of who will do what changes to these tables need to be established and the appropriate tools added where needed. Having programmers do this kind of maintenance is wasteful of their time.

4. Design

Technical lead should provide a brief description of how this will be implemented in the code.

5. Deployment Checklist

Documentation? Systems/hardware/networking things needed for deployment?

6. Test Plan

6.1 Internal Testing

6.2 Sponsor Testing

6.3 Integration/Regression Tests


APPROVED: I acknowledge that my request is fully contained in this MR, and if the Open Sky (or other NIS or PST developers) deliver exactly what I specified, I will be happy.

ACCEPTED: I acknowledge that I have validated the completed code according to the acceptance tests, and I am happy with the results.

Written ALERT! - OpenSky - 20 Nov 2007
Checked - - - - -
Approved by Scientific Sponsor - - - - -
Accepted/Delivered by Sponsor - - - - -

  • Use %X% if MR is not complete (will display ALERT!)
  • Use %Y% if MR iscomplete (will display DONE)

Discussion Area

-- OpenSky - 20 Nov 2007
Topic revision: r2 - 2007-11-21, OpenSky
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