Message-ID: <1780809326.11691.1416769714380.JavaMail.email@example.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_11690_1485469043.1416769714380" ------=_Part_11690_1485469043.1416769714380 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
This document lays out the development priorities and plans for the GumT= ree software version 1.6. The aim of this plan is to provide an overview of= works that are committed in the current development iteration cycle. This = is a living document and is subject to change based on the project priority= .
The overall theme for version 1.6.x is about cleaner design and improvin= g user experience. The aim is to create a software stack that helps to prod= uce science more quickly. A number of infrastructural tasks, including new = better GumTree middleware support, will run in background. Version 1.6.x wi= ll set a new milestone for the GumTree development.
The deployment date of GumTree software for individual instrument is dep= ended upon reactor cycle and instrument maintenance schedule. However, the = release date for the GumTree Platform (or the base NBI target for developme= nt) should be fixed, so that the development process is agile (with short i= teration) and predictable.
At the end each final release, a change log and brief new feature descri= ption must be supplied with the artifacts. After each iteration, a new targ= et will be produced for internal development use, and all developers need t= o sync with this latest target. Developers will need to meet together for q= uick briefing on the new features introduced in each iteration.
Each release is set to 4 months long, with 1 week planning, four 3 week = long iteration, and 3 week endgame (final integration test, documentation a= nd release work). All phases may be adjustable to fit operation needs, but = we usually do not encourage this.
However, due to the build process refactoring, our release schedule has = been modified. This release will feature 5 major releases with 8 mont= h release schedule.
Planning: 7th March 2011 - 1st April 2011 (4 week)
Technology Investigation: 4th April 2011 - 29th April 20= 11 (4 week)
Iteration 0: 2nd May 2011 - 3rd June 201= 1 (4 week) - version 1.6.0
Iteration 1: 6th June 201= 1 - 1st July 2011 (4 week) - version 1.6.1
Iteration 2: 4th July 2011 - 19th July 2011 (4 week) - version 1.6.2
I= teration 3: 1st August 2011 - 26th August 2011 (4 week) - version = 1.6.3
Iteration 4: 29th August 2011 - 23rd September= 2011 (4 week) - version 1.6.4
Endgame: 26th Septemb= er 2011 - 14th October 2011 (3 week) - version 1.6.5 (official 1.6.x releas= e)
An instrument theme is a high level task description on what use require= ment we need to fulfil for this release of GumTree. Those requirements come= from instrument scientists meeting, instrument maintenance jobs (software = bug fixes), and refactoring tasks for making software maintainable.
No scheduled plan for Platypus in this version.
No scheduled plan for Pelican in this version.
No scheduled plan for NESCA in this version.