Skip navigation

Jive Talks

1 Post authored by: marty.kagan

For my first Jive Talks post, I'd like to talk about some of the changes we're making to the release train in 2008: Internally, we are committed to continuing with an agile development process based on 3 week iterations. At the end of each of these cycles, we will make the current code available as an alpha or beta beta release for developers. Information about how to sign up for the 2.0 Beta Program should be available soon! Externally, we are aiming to launch major/minor releases once a quarter. Clearspace 2.0 has been (and continues to be) an ambitious undertaking, but we're still shooting for a release in early April. Subsequent releases (2.1, 2.2, 2.3) should land in July, October, January, etc. We're looking at adding some very exciting features this year, but I'll let others tell that story...

 

On the support side, we will continue to provide patch releases for up to 12 months after any major or minor release. These point releases (2.0.1, 2.0.2, etc.) will be reserved strictly for bug fixes, and contain no new functionality.  As in the past, these will be released on a 3-week cycle to give the Software Quality Assurance team sufficient time for testing. We've planned for 3-4 scheduled patch releases after every major/minor release.  After that, we will do patches on an ad hoc basis to address any severity 1 or 2 issues that may arise.

 

The 1.x series went into maintenance mode starting with 1.10. There is a 1.10.1 patch release scheduled for next week, and again, we will continue to do patches on an as-needed basis to address critical issues for up to 12 months, after which we will ask customers to upgrade to 2.x, in order to stay on a supported release.

 

On a personal note, I've been having a great time since joining the Jive development team in November. As you may know, we're doing a lot of hiring this year, and I would love to hear from you if you're interested in joining us!

Filter Blog

By date: By tag: