How is the Continuum development roadmap organized?
Basically the roadmap should link to specific design documents that detail features that are being developed, being considered for development, or are being just having their tires kicked.
What is the current roadmap?
The current roadmap is to actually get continuum released. The vast majority of any new functionality is basically considered to be complete for the 1.1 release of continuum and anything remaining should be pushed off to a point release or until the next version of continuum altogether.
| Feature | Jira | Status |
|---|---|---|
| Migration to webwork 2.2.2 for UI | 771 |  |
| Reimplementation of authentication/authorization management | 542, 513 | |
| Stop Build ability under certain conditions | 389,667 | |
| Build on Dependency changes | 58, 137 | |
| Project Groups | 30, 289,290, 291,292 | |
| Test Result Summary Page | 309 | |
| Add Projects page work | 741 | |
| resolve jpox issues, get jdo working well | 740 | |
 |
A great many new features and fixes are not captured in this table |
What is on deck for development?
| Feature | Jira | Status |
|---|---|---|
| relocate db and temp data | 169 | |
| continuum profiles and installation screens | 44, 59 | |
| field validation | 755 | |
| large project useability | ||
| Error handling and diagnosis | ||
| enhance project groups | 520 | |
| view build schedule | 46 | |
| Integrate GBuild | 563 | |
| Customizable Mail Templates | ||
| Build promotion | ||
| Import/Export Support for Configurations from other CI | ||
| Skinning | ||
| JIRA/Bugzilla integration | ||
| Improved Maven 1.0 integration | ||
| RSS Support | ||
| Concurrent builds | ||
| Alternate build trigger mechanisms | ||
| Access to archived results | ||
| Build escalation | ||
| Template configurations | ||
| New project builders | ||
| Trigger plugins |
See also: Continuum 1.2 Design Discussions
Labels
(None)