I'm pretty sure we can just rename the version in JIRA. On Wed, Dec 17, 2008 at 10:33 AM, Willem Jiang <[email protected]>wrote:
> +1 for the use the 1.6 as the new release version of Camel. > Here is a question for the JIRA version. > Is there any batch tool can help us to change the version from 1.5.1 to > 1.6? > > Willem > > Hadrian Zbarcea wrote: > > Hi, > > > > Just got back from a long vacation. Wow, it felt good :). > > > > Sure, let me take a look at what outstanding. The branch is 1.x so we > > could go with a 1.6 (and I think that would be my preference too). Is > > there a consensus on the version number? > > > > Cheers > > Hadrian > > > > On Dec 17, 2008, at 3:40 AM, Claus Ibsen wrote: > > > >> Hadrian > >> > >> Any update on when you have the time to cut a 1.5.1 RC? > >> We have some rather important bunch of fixes in it. > >> > >> > >> > >> On Wed, Dec 3, 2008 at 6:23 PM, Claus Ibsen <[email protected]> > >> wrote: > >>> Hi > >>> > >>> I think we should start getting a RC for 1.5.1 out of the door this or > >>> start of next week. > >>> > >>> /Claus Ibsen > >>> Apache Camel Committer > >>> Blog: http://davsclaus.blogspot.com/ > >>> > >>> > >>> > >>> On Mon, Dec 1, 2008 at 5:30 PM, Hadrian Zbarcea <[email protected]> > >>> wrote: > >>>> 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/ > >>>> > >>>> > >>> > >> > >> > >> > >> -- > >> > >> /Claus Ibsen > >> Apache Camel Committer > >> Blog: http://davsclaus.blogspot.com/ > > > > > > -- Cheers, Jon http://janstey.blogspot.com/
