E-mail
Release 3 Beta 1
The purpose of R3Beta1 (First Beta release for Release 3), is to provide a base set of R3 Milestones integrated and working in an R3 beta system that Marine IO users can try out.
Schedule
The planned schedule for R3Beta1 is April 11th, 2014.
Release Content
The release is planned to include the following completed Milestones:
- M087 Data processing workflow management (Will need UI enhancements no UI tests exist)
- M100 Marine Device Activation (May need UI enhancements??)
- M112 Geospatial Search (Will need UI enhancements no UI tests exist)
- M114 Coverage Model Integration (no UI enhancement - all SW tests pass)
- M142 Agent Framework Integration
- M155 Resource Operations Framework (May need UI enhancements??)
- M156 Schema Versioning (Will need UI enhancements no UI tests exist)
The release is planned to include the following Defect Fixes:
- OOIION-869 Add ansynchronous requests to face pages to speed up display
- OOIION-1386 Container message processing inefficient for larger messages
- OOIION-1731 Uptime not displaying properly for a dataset agent for a platform
- OOIION-1749 Dataset Driver Persistance Failure
The release is planned to include the following new MI Dataset Agent Drivers:
- [Pioneer FLORT_KN]
- [Pioneer PARAD_K]
- [Pioneer WFP_ENG]
See release notes:
- UI Bug Fixes. See: [Release 3 Beta 1 UI Release Notes]
- Services Bug Fixes. See: [Release 3 Beta 1 Services Release Notes]
Test Plan
The release will be tested over a few week period in March and April. The following test plan will be used:
Milestone Status
M087 Data processing workflow management
No UI-tests or documentation exist.
Otherwise, documentation complete.M114 Coverage Model Integration :
all tests pass, documents completed
M100 Marine Device Activation:
documentation complete
no UI requirements
M112 Geospatial Search
No UI-tests or documentation exist.
Otherwise, documentation complete.
M114 Coverage Model Integration :
all tests pass, documents completed
M142 Agent Framework Integration :
Test exist and pass for requirements NEW Marine CyberPoP - 4, 5.
Test exist but fail for requirements NEW Marine CyberPoP - 7. But this is claimed to be due to insufficient documentation of how to set up and run.
Tests do not exist for requirements NEW Marine CyberPoP - 6, 11, 12, 13, 14,
M155 Resource Operations Framework
documentation complete
M156 Schema Versioning :
All non-UI tests pass. Documents completed
No UI-tests or documentation exist.
Specific R3Beta1 Integration and Test Tasks
For R3Beta1 to be successful, the following integration and test tasks must be performed:
 | Priority tasks are in bold DAD = Dataset Agent Driver, and DPA = Data Product Algorithm |
- Resolve coverage migration for R2 to R2 and test on ion-dev to make sure it works (Casey/Matthew, Jamie) (NOTE: Migration is being deferred to R3Beta3 or in transition)
- Stand up a full R3 Alpha test system with full preload (Adam, Jamie) (DONE)
- Work with dev team to prepare milestone pages with testing and requirements verification details (Bill and Prashant) (DONE)
- Add Station Papa and Pioneer driver deployments to ion-alpha system (Jamie) (In progress)
- Execute testing of R3 alpha (fully preloaded) system to verify new code has not impacted existing functionality (Bill and Prashant) (In Progress)
- Setup R3 test system with migration procedures. This needs individual migration script to be added. (Jamie, Luke, Michael, Matthew/Casey) (NOTE: Migration is being deferred to R3Beta3 or in transition)
- Execute testing of R3 alpha (fully MIGRATED) system to verify new code has not impacted existing functionality and that Migration worked successfully (Bill and Prashant) (NOTE: Migration is being deferred to R3Beta3 or in transition)
- Stand up a full R3 Beta system (Adam, Bahadir, Jamie) (In Progress)
- Deploy R3Beta1 software with full preload to new R3 Beta system - including Station Papa and Pioneer drivers (Jamie)