Release 3 Beta 3

Release 3 Beta 3

The purpose of R3Beta3 (Third and final Beta release for Release 3), is to provide the full set of R3 Milestones integrated and working in an R3 beta system that Marine IO users can try out. This will be the release used as part of the Initial Operational Capability (IOC) review.

Schedule

The planned schedule for R3Beta2 is June 27th, 2014.

Release Content

The release is planned to include the following completed Milestones:

• [M057 OGC External data catalog cross-referencing |M057 OGC External data catalog cross-referencing
• M153 Exchange Framework Extension
• M059 DAP Integration
• M117 Multi Source Coverage
• M086 Data Calibration Management
• M184 Integrate and revise message security and certification
• M193 Deployment and Station Management Service
• M185 Non-web-UI user agent support
• M047 IPython Notebook ION Service Integration
• M137 Instrument Device Test Capabilities
• M030 Marine Asset Tracking

The release is planned to include the following Defect Fixes:

• Unknown at this point

The release is planned to include the following new MI Dataset Agent Drivers:

• Possibly updated Station Papa Glider Drivers. Still TBD

See release notes:

• UI Bug Fixes. See: [Release 3 Beta 3 UI Release Notes]
• Services Bug Fixes. See: [Release 3 Beta 3 Services Release Notes]

Test Plan

The release will be tested over a few week period in June, 2014. The following test plan will be used:

• [Release 3 Beta 3 Verification Test Plan]

See release notes:

• UI Bug Fixes. See: [Release 3 Beta 3 UI Release Notes]
• Services Bug Fixes. See: [Release 3 Beta 3 Services Release Notes]

Specific R3Beta3 Integration and Test Tasks

For R3Beta3 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

• Update the R3 Alpha test system with a new full preload (Jamie)
• Work with dev team to prepare milestone pages with testing and requirements verification details (Prashant + ?)
• Add all outstanding driver deployments to ion-alpha system (Jamie)
• Execute testing of R3 alpha (fully preloaded) system to verify new code has not impacted existing functionality (Bill and Prashant)
• Setup R3 test system with migration procedures. This needs individual migration script to be added. (Jamie, Luke, Michael, Matthew/Casey)
• 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)
• Deploy R3Beta1 software and execute fully tested and working migration process to R3 Beta system - including new MI drivers (Jamie)