Page History

...

Before development is begun, it should be clear the business owner considers this change critical and requires an immediate fix. An email message describing the situation must be sent to Frank Quern (fquern@mit.edu), with a copy sent to John Tuttle (jtuttle@mit.edu), to facilitate consideration of the critical fix. After review Frank will request approval to migrate the fix to Test from one of the business members of the Steering Committee.

Development will be performed in SF2 both before and after the support and enhancement packs been applied. While the support and enhancement packs are being applied to SF2, SF2 will be unavailable for development. If an emergency arises during this period, SF8 will be used for development.

1. If necessary, revert each development object to be changed to the version currently in Production. In-process changes should be saved as a non-transportable copy of the object, as a downloaded text file, or as a printed listing.
2. Change the development object(s) to implement the required fix.
3. Perform unit testing in SF2.
4. Transport the fix to SF5/SH1 /SH2& SH3 (as part of SP application process).
5. Perform the usual regression and user-acceptance testing in SF5/SH1.
6. Perform testing required to confirm the proper functioning of the fix in SH2SH3.
7. Obtain the required approvals.
8. Transport the fix to Production.

...