PerfSONAR v3.0 timeline

Planning for 3.0

Task: Finish the Product Specification Document, Hand over document update and all templates updated where necessary
- Description: Complete the document and replace the “MDM-perfSONAR Bundle 3.0” wiki page with it.
- Pre-requirements: Input from development, testing and visualization teams about document structure.
- Date: 21 November

Task: Testing Team – Draft Test Plan
- Description: Testing Team manager to deliver a template/example that will serve as a Draft Test Plan, so that the other testers can follow and do the same for each service that is of their responsability to test.
- Pre-requirements: Product Specification Document.
- Date: 09 November

Task: Disseminate to developers installation and update innovations for 3.0
- Description: Guilherme to disseminate information to Development Teams about using TAR files and RPMs on this release.
- Pre-requirements: none.
- Date: 14 December

Task: Disseminate to developers visual configuration innovations for 3.0
- Description: Michalis to disseminate information to Development Teams about using servlets for visual configuration of each service for this release.
- Pre-requirements: none.
- Date: 21 December

Task: Assist developers in generating RPMs, tar files and servlets
- Description: Based on the dissemination provided in the previous tasks, these new features will need to be integrated with all the services part of MDM-perfsonar-bundle 3.0. Guilherme and Michalis have to supervise the related work.
- Pre-requirements: Product Specification Document, Information about new features to be disseminated to involved developers
- Date: 21 December

Task: Development Teams – Software Specifications documents and change logs
- Description: The Development Teams to deliver the documents that define the features and also the syntax and semantics of the service they are developing, obeying the templates given by the Release Team. These documents are: Functional Specification of service, Interface specification, Specification of Ant targets / Installation Instructions, Sample configuration files, Metadata configuration files. Developers also have to maintain updated Change Logs for their services in the doc directory of SVN, and keep them updated at all time (including bug fixes) .
- Pre-requirements: Templates and samples written by Release Management.
- Date: 21 December

Task: Release Team – Verify Software Specifications documents
- Description: The Release Team to verify Change Logs and the documents delivered by Development Teams. These documents are, for each service: Functional Specification of service, Interface specification, Installation Instructions, Sample configuration files, Metadata configuration files.
- Pre-requirements: Software Specifications documents delivered.
- Date: 04 January

Task: Testing Team – Testing specifications document, Test Report template and testing scripts
- Description: Testing Team to deliver the final test plan with detailed test cases, already taking into account with the specification documents written by developers. Along with the test specifications, the testing team will need to prepare a test report template. This template will include a table for “Yes” and “No” answers, that will the be used for writing reports on each test case of the micro-release that is being tested.
- Pre-requirements: Draft test plan and specifications documents written by developers
- Date: 11 January

Task: Development Teams and Testing Team – First Release Candidates are delivered and testing starts as they are delivered
- Description: Development Teams to start providing Release Candidates for testing. Testing Team to apply testing scripts and test Release Candidates.
- Pre-requirements: Draft test plan and specifications documents written by developers
- Date: 18 January

Task: Development Teams – Provided first Release Candidates for all services
- Description: Development Teams to have provided all Release Candidates for micro releases for testing.
- Pre-requirements: none
- Date: 08 February

Task: Testing Team – Tests finished, delivered Test Reports
- Description: Testing team to deliver completed Test Reports with the results of all testing, even of those services that needed re-testing and more Release Candidates.
- Pre-requirements: all Release Candidates delivered and tested
- Date: 28 March

Task: Release Team – Write final product manual, including change logs
- Description: Release team to write the full product manual, including change logs for each service. Afterwards, ask the development teams to review the final manual.
- Pre-requirements: Have all documents and change logs from Development teams.
- Date: 28 March

Task: Release Team – First Release Candidate of MDM perfSONAR Bundle 3.0 ready for testing
- Description: Release team to make available the first Release Candidate for this Bundle.
- Pre-requirements: All micro-releases tested and accepted, bundle installer scripts ready.
- Date: 03 April

Task: Release Team – Announce final release
- Description: Release team to announce the final release, after all necessary Release Candidates are fully tested and accepted by developers, users and testing team.
- Pre-requirements: all tasks fulfilled.
- Date: ??