Task #3947
Create new status variables for MNDeployment and update status on existing MNDeployments as needed
100%
Description
Per email discussions, we will use New, Planning, Developing, Testing, Operational, Deferred, and Closed as the status values for MNDeployment trackers.
See http://mule1.dataone.org/OperationDocs/member_node_deployment/mn_checklist.html (or http://mule1.dataone.org/OperationDocs/member_node_deployment/mn_checklist_working.html) for definitions of planning, developing, testing, and operational.
New means that there isn't any formal sort of work going on for the MN. Deferred means that we've put this on the back burner. Closed is that no future work is expected at this time. We're using Closed in preference to Rejected. While Rejected is understood within a development context, it carries some connotations we'd rather not use for MN's.
History
#1 Updated by Bruce Wilson almost 11 years ago
- Status changed from In Progress to Testing
- % Done changed from 10 to 90
The current MNDeployment status values are
* New (no work or maybe some initial discussions),
* Planning (work is in progress to scope and plan out the work),
* Developing (there is active work to implement the plan),
* Testing (the MN is working to put data into sandbox (as opposed to dev) to validate that the data going into DataONE is valid/correct),
* Operational (live data is available in the production instance),
* Deferred (some work or discussions have started, and there's an intent to get back to this, though not necessarily a defined date where that will happen)
* Closed (we do not expect that this organization will become a MN)
* Dup-Closed (the tracker is a duplicate of another MNDeployment, used so that we can differentiate based just on status between candidate MN's that didn't pan out and those where we got the same thing on the list twice).
#2 Updated by Bruce Wilson over 9 years ago
- Status changed from Testing to Closed
- % Done changed from 90 to 100
- translation missing: en.field_remaining_hours set to 0.0
