It's certainly the safer option... as long as everybody understands that
> Yes - please promote it - then it's easy to spot and consume.
> I have some projects with Camel and can help test - that should be
> pretty good for spotting regressions.
>
> 2011/10/24 Christian Schneider<
[hidden email]>:
>> We should name it 2.9.0-rc1 and also promote it. If not then not many people
>> will use it at all.
>>
>> Christian
>>
>> Am 24.10.2011 14:44, schrieb Hadrian Zbarcea:
>>>
>>> Yeah, that sounds good. I am planning on cutting an rc1 tomorrow then.
>>> Should the version be *-2.9.0-rc1? or just go with the regular 2.9.0, just
>>> not promote it (drop after tests). There are pros and cons for both. I am
>>> not sure what my preference would be. I assume users will not use this rc,
>>> it'll be just for more thorough testing, so it could be used from
>>> repository.a.o (without promoting) and then 2.9.0 would be ok, however it
>>> adds some confusion. 2.9.0-rc1 is definitely safer. I don't think we need a
>>> vote to release the rc1 either, or do we?
>>>
>>> Ideas?
>>> Hadrian
>>>
>>> On 10/24/2011 08:36 AM, Claus Ibsen wrote:
>>>>
>>>> On Mon, Oct 24, 2011 at 2:33 PM, Hadrian Zbarcea<
[hidden email]>
>>>> wrote:
>>>>>
>>>>> I assume the proposal to do an RC first still stands, correct?
>>>>>
>>>>
>>>> Yeah IMHO that could be a good idea. Also in light that there is 80+
>>>> JIRA tickets assigned to 2.9.0.
>>>> So we may be able to cut a RC sooner, and then have some JIRA tickets
>>>> which we want to include in the GA release.
>>>> And then after the RC we can work on those tickets.
>>>>
>>>>
>>>>
>>>>> Hadrian
>>>>>
>>>>> On 10/24/2011 08:26 AM, Christian Schneider wrote:
>>>>>>
>>>>>> Sounds good to me.
>>>>>> I propose to aim for a release and vote in about a week.
>>>>>>
>>>>>> Christian
>>>>>>
>>>>>>
>>>>>> Am 24.10.2011 13:55, schrieb Claus Ibsen:
>>>>>>>
>>>>>>> Hi
>>>>>>>
>>>>>>> Its almost 3 months since 2.8.0 was released
>>>>>>>
http://camel.apache.org/2011/07/25/camel-280-released.html>>>>>>>
>>>>>>> I think we should start considering a Camel 2.9.0 release. And thus I
>>>>>>> suggest to start focusing on bug fixes, and unit test fixes etc.
>>>>>>> And to keep an eye on CI servers to fix test and other issues reported
>>>>>>> there.
>>>>>>>
>>>>>>> Also I suggest to look at unresolved Camel 2.9.0 tickets in JIRA and
>>>>>>> possible move tickets to 2.10 or 2.9.1 if that is possible.
>>>>>>> Also if there is tickets which you think is a good/must have in 2.9.0
>>>>>>> then I suggest to post here with the ticket numbers.
>>>>>>> And of course to work on those tickets so they get resolved in the
>>>>>>> near time.
>>>>>>>
>>>>>>> We have 84 open tickets which has been assigned to 2.9.0. I think
>>>>>>> that's too much and encourage you to look at those
>>>>>>> and either move/fix the tickets so we can get this down to a
>>>>>>> management number of tickets to be resolved in the near time.
>>>>>>>
>>>>>>> Camel 2.9 open tickets:
>>>>>>>
>>>>>>>
>>>>>>>
https://issues.apache.org/jira/secure/IssueNavigator.jspa?sorter/field=issuekey&sorter/order=DESC>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>>
>>
>>
>> --
>> Christian Schneider
>>
http://www.liquid-reality.de>>
>> Open Source Architect
>> Talend Application Integration Division
http://www.talend.com>>
>>
>
>
>
Locked
