Producing the kit is not the main issue. Quite a few of us spend time
downloading the rc, running the demos, looking at content of the
distro, checking if all the artifacts are there, the manual is
generated ok and so forth. This is time consuming. Then there is the
voting process. Sometimes we get -1s for a bad kit (although that
didn't happen in a while afairc), sometimes because a committer has a
strong opinion about a jira issue that must go in the release, which
puts us back to square one. All in all the process for a release
candidate takes 3-5 days.
Cheers,
Hadrian
On Dec 1, 2008, at 11:09 AM, Martin Gilday wrote:
Speaking as an end user I'd quite like to see maintenance releases
coming out of Camel. You guys are really great at responding to
users'
feedback and fixing bugs but that is in vain if they have to wait
for 3
months until the next major rlease. Users can be uncomfotable running
against snapshots in production, so a fix release every month or so
would make us feel cosy. As Maven is being used is there much more to
releasing other than a few svn copy commands and a maven deploy? If
it
is seen as a hassle then can we look at simplifying it so that it can
happen more often without taking up committers time?
----- Original message -----
From: "Jon Anstey" <[EMAIL PROTECTED]>
To: [email protected]
Date: Mon, 1 Dec 2008 10:13:38 -0330
Subject: Re: Release camel 1.5.1 this month?
Do you think we need another release so soon? We just released 1.5 a
month
ago :) I'm just saying its a bit of work for you to put a release out,
isn't
it?
On Mon, Dec 1, 2008 at 10:06 AM, Hadrian Zbarcea <[EMAIL PROTECTED]>
wrote:
There are 57 issues fixed on the 1.5.1 branch so far and a few more
coming
in the following couple of weeks.
I'd suggest releasing a 1.5.1 before the end of the month. What do
you
think?
Hadrian
--
Cheers,
Jon
http://janstey.blogspot.com/
