Message-ID: <777120354.3576.1369390008980.JavaMail.email@example.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_3575_1681157819.1369390008979" ------=_Part_3575_1681157819.1369390008979 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
This document lays out th= e development priorities and plans for the GumTree software version 1.6. Th= e 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 fo= r version 1.6.x is about cleaner design and improving user experience. The = aim is to create a software stack that helps to produce science more quickl= y. A number of infrastructural tasks, including new better GumTree middlewa= re support, will run in background. Version 1.6.x will set a new milestone = for the GumTree development.
The deployment date of GumTree software for individual instrument is = depended upon reactor cycle and instrument maintenance schedule. However, t= he release date for the GumTree Platform (or the base NBI target for develo= pment) should be fixed, so that the development process is agile (with shor= t iteration) and predictable.
At the end each final release, a change= log and brief new feature description must be supplied with the artifacts.= After each iteration, a new target will be produced for internal developme= nt use, and all developers need to sync with this latest target. Developers= will need to meet together for quick briefing on the new features introduc= ed in each iteration.
Each release is set to 4 months long, with 1 we= ek planning, four 3 week long iteration, and 3 week endgame (final integrat= ion test, documentation and release work). All phases may be adjustable to = fit operation needs, but we usually do not encourage this.
However, d= ue to the build process refactoring, our release schedule has been modified= . =C2=A0This release will feature 5 major releases with 8 month release sch= edule.
Planning: 7th March 2011 - 1st April 2011 (4 =
Technology Investigation: 4th April 2011 - 29t= h April 2011 (4 week)
Iteration 0: 2nd May 2011 - 3r= d June 2011 (4 week) - version 1.6.0
Iteration 1: 6t= h June 2011 - 1st July 2011 (4 week) - version 1.6.1
Iteratio= n 2: 4th July 2011 - 19th July 2011 (4 week) - version 1.6.2
= Iteration 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: 26= th September 2011 - 14th October 2011 (3 week) - version 1.6.5 (official 1.= 6.x release)
An instrument theme is a high level task description on what use r= equirement we need to fulfil for this release of GumTree. Those requirement= s come from instrument scientists meeting, instrument maintenance jobs (sof= tware bug fixes), and refactoring tasks for making software maintainable.= p>
= No scheduled plan for Platypus in this version.
No scheduled plan for Pelican in this versi= on.
No scheduled pla= n for NESCA in this version.