You are viewing an old version of this page. View the current version.
Compare with Current ·
View Page History
Contact: | |
|---|---|
Tracker: | https://jira.codehaus.org/browse/GEOT-4182 |
Tagline: | is it time? |
Children: |
Description
Switch to a timed release cycle for GeoTools.
The expected benefits are:
- reducing the delay between releases
- predictability for our customers (and downstream projects)
- reduce the significance of a feature missing a release (just catch the next release train)
- easier to plan, and acquire resources, to make each release
This proposal requires:
- significant automation (to reduce the time taken to prepare a release)
- resource commitment from participating organisation
This proposal is made in conjunction with GSIP 77 - Time boxed release model - review this page for more details including proposed release schedule
- stable: monthly release, available for bug fixes,new features that do not change API or stability
- master: six month release cycle
- 1-4: initially open for change proposals
- 5-6: locked down from release candidate through to release
Community support:
- uDig PSC supports this release cycle, will remain on trunk and may issue the occasional "milestone" release
Status
This proposal has the support of:
- Andrea Aime +1
- Ben Caradoc-Davies +1
- Christian Mueller +1
- Ian Turton +0
- Justin Deoliveira +1
- Jody Garnett +1
- Simone Giannecchini +0
Tasks
no progress |
| done |
| impeded |
| lack mandate/funds/time |
| volunteer needed |
|---|
JD: Automation for release process- JG: Updated developers guide as listed below
Documentation Changes
- Release - new procedure page documenting the release cycle
- How to Cut a release - provide instructions on how to run the scripts
- Roles - responsibilities updated to reflect release cycle restrictions
- GeoTools change proposal - update to note the restrictions placed on proposals during the release cycle
Labels