Cut a release kit is not hard thing, It just takes 4 hours even with my poor 64KBS uploading internet connection.

The hard part is we need to make sure the branch is ready for release.
It could be lots of work to test the snapshot to avoid cutting the release several times.

It could be better if we can make the release branch stable for a week to run some addition tests.

Just my 2 cents.

On Fri Dec  2 06:57:17 2011, Christian Müller wrote:
@Hadrian: Coming back to your proposal to have micro releases after 4 - 6
weeks (ReRo ->  [1]). Originally I was thinking about to have micro releases
after 6 - 8 weeks. But I thought this is too often because of the work for
the release manager and all other people who are involved (testing the
release, ...). But may we will see more release managers in the future
(like me) and than we may can handle the work. We can start with a 6 weeks
cycle and see how it works for us. Sounds good for all of you?

[1] http://en.wikipedia.org/wiki/Release_early,_release_often

Best,
Christian



--
Willem
----------------------------------
FuseSource
Web: http://www.fusesource.com
Blog:    http://willemjiang.blogspot.com (English)
         http://jnn.javaeye.com (Chinese)
Twitter: willemjiang
Weibo: willemjiang

Reply via email to