-Original Message-
From: Chip Childers [mailto:chipchild...@apache.org]
Sent: Friday, November 15, 2013 6:28 AM
To: dev@cloudstack.apache.org
Subject: Re: [ASF4.2.1] Release Notes
IMO, we should kill the CHAGES file and just get the release notes document
under control. I'm fi
t I will veto an RC
>>>>>>>>>that
>>>>>>>>> does not have list of bugs fixed and proper upgrade path documented
>>>>>>>>> (minimum of a fix from 4.2.0 upgrade docs). Separate repo of the
>>>>>>>>>docs
&
ate repo of the
> >>>>>>>>docs
> >>>>>>>>or
> >>>>>>>> not.
> >>>>>>>>
> >>>>>>>> Right now I see that the bugs fix list points to a jira filter.
> >>>&
>>>>>>This
>>>>>>>>is
>>>>>>>> not consistent with the way it was done in prior releases (explicit
>>>>>>>> listing) and in 4.2 (which pointed to the RN). We need consistency.
>>>>>>>>What
>>> not consistent with the way it was done in prior releases (explicit
>>>>>>>> listing) and in 4.2 (which pointed to the RN). We need consistency.
>>>>>>>> What
>>>>>>>> happens if someone changes this jira filter ?
&g
istency.
>>>>>>> What
>>>>>>> happens if someone changes this jira filter ?
>>>>>>>
>>>>>>> I also would like to see the results of the test matrix for 4.2.1
>>>>>>> running within jenkins.buildacloud.org.
ens if someone changes this jira filter ?
>>>>>>>
>>>>>>> I also would like to see the results of the test matrix for 4.2.1
>>>>>>> running within jenkins.buildacloud.org. This
>>>>>>> http://jenkins.buildacloud.org/view/cloudstack-q
>>>>>> PS: I did test it and did the usual smoke test
>>>>>>
>>>>>> so -1 (binding) at this time
>>>>>>
>>>>>> -sebastien
>>>>>>
>>>>>>
>>>>>&g
did the usual smoke test
>>>>>>
>>>>>> so -1 (binding) at this time
>>>>>>
>>>>>> -sebastien
>>>>>>
>>>>>>
>>>>>> On Nov 14, 2013, at 4:20 PM, Chip Childers
&g
>>>>voting
>>>>>> during doc finalization. If we announce before docs, it hurts us.
>>>>>> I'm against another announcement that goes out with the docs in poor
>>>>>> shape.
>>>>>>
>>>>>
gt;>>
>>>>> On Thu, Nov 14, 2013 at 3:44 PM, Animesh Chaturvedi
>>>>> wrote:
>>>>>> Unless there are objection to the RC, I would prefer to have it
>>>>>> released and make the announcement sooner and showcase in collab
>>
On Fri, Nov 15, 2013 at 03:14:48AM -0500, Sebastien Goasguen wrote:
> I also would like to see the results of the test matrix for 4.2.1
> running within jenkins.buildacloud.org. This
> http://jenkins.buildacloud.org/view/cloudstack-qa/ runs against
> master and has been failing for a while.
>
Bi
14/11/13 8:12 pm, "Sebastien Goasguen" wrote:
>>>>>
>>>>>> Anyway we can wait next week to release.
>>>>>>
>>>>>> quite a few of us will be together in Amsterdam, we can dedicate a
>>>>>> hacka
2 pm, "Sebastien Goasguen" wrote:
>>>>
>>>>> Anyway we can wait next week to release.
>>>>>
>>>>> quite a few of us will be together in Amsterdam, we can dedicate a
>>>>> hackathon session to 4.2.1 , make sure RN
ake sure RN are good, upgrade path
>>>> etcŠthen testŠ.
>>>>
>>>> I'd recommend keeping the vote open until then.
>>>>
>>>> -sebastien
>>>>
>>>>
>>>> On Nov 14, 2013, at 5:57 AM, Radhika Puth
#x27;d recommend keeping the vote open until then.
>>>
>>> -sebastien
>>>
>>>
>>> On Nov 14, 2013, at 5:57 AM, Radhika Puthiyetath
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> The master has the most up-
in Amsterdam, we can dedicate a
>>> >>>hackathon session to 4.2.1 , make sure RN are good, upgrade path
>>> >>>etcŠthen testŠ.
>>> >>>
>>> >>>I'd recommend keeping the vote open until then.
>>> >>>
>&
pgrade path
>> >>>etcŠthen testŠ.
>> >>>
>> >>>I'd recommend keeping the vote open until then.
>> >>>
>> >>>-sebastien
>> >>>
>> >>>
>> >>>On Nov 14, 2013, at 5:57 AM, Radhika
: Sebastien Goasguen; Alok Kumar Singh
Subject: Re: [ASF4.2.1] Release Notes
I agree - announcing a release prior to docs availability hurts the project
because users fail in installation and upgrades.
The gate in my mind is docs readiness - thats an integral part of the release
process, even if the
>>>
> >>>I'd recommend keeping the vote open until then.
> >>>
> >>>-sebastien
> >>>
> >>>
> >>>On Nov 14, 2013, at 5:57 AM, Radhika Puthiyetath
> >>> wrote:
> >>>
> >>>> Hi,
> >
rote:
>>>
>>>> Hi,
>>>>
>>>> The master has the most up-to-date RN for 4.2.1.
>>>>
>>>> From: Abhinandan Prateek
>>>> Sent: Thursday, November 14, 2013 2:22 PM
>>>> To: CloudStack Dev
>>>> C
;>
>>-sebastien
>>
>>
>>On Nov 14, 2013, at 5:57 AM, Radhika Puthiyetath
>> wrote:
>>
>>> Hi,
>>>
>>> The master has the most up-to-date RN for 4.2.1.
>>>
>>> From: Abhinandan Prateek
>>> Sent: Thursday, Nove
, at 5:57 AM, Radhika Puthiyetath
> wrote:
>
>> Hi,
>>
>> The master has the most up-to-date RN for 4.2.1.
>>
>> From: Abhinandan Prateek
>> Sent: Thursday, November 14, 2013 2:22 PM
>> To: CloudStack Dev
>> Cc: Radhika Puthiyetath
>> Subje
th
> wrote:
>
>> Hi,
>>
>> The master has the most up-to-date RN for 4.2.1.
>>
>> From: Abhinandan Prateek
>> Sent: Thursday, November 14, 2013 2:22 PM
>> To: CloudStack Dev
>> Cc: Radhika Puthiyetath
>> Subject: Re: [ASF4.2.1] Release
you are right, I now casted a vote and we are at +2 (I had a tentative
+1 before pending some tests:)
On Thu, Nov 14, 2013 at 5:16 PM, Chip Childers wrote:
> On Thu, Nov 14, 2013 at 05:06:41PM +0100, Daan Hoogland wrote:
>> Ok, i don't want to press for a release. We'll see (i think we are at
>>
On Thu, Nov 14, 2013 at 05:06:41PM +0100, Daan Hoogland wrote:
> Ok, i don't want to press for a release. We'll see (i think we are at
> +2 binding???)
1 - mine
ine. Maybe I'm missing something here, but without reliable documented
>> steps of what is meant to work, it's hard to test the upgrade process.
>>
>> - Si
>>
>> ____________
>> From: Chip Childers
>> Sent: Thursday, No
g here, but without reliable documented steps
> of what is meant to work, it's hard to test the upgrade process.
>
> - Si
>
>
> From: Chip Childers
> Sent: Thursday, November 14, 2013 9:40 AM
> To: dev@cloudstack.apache.org
> C
On Thu, Nov 14, 2013 at 04:49:26PM +0100, Daan Hoogland wrote:
> I am almost +1 on this. If we can at least give the RC to people at
> ccc. Not having a new package to show off next week is a missed
> opportunity.
>
> How about trying to close the vote on wednesday night?? If no
> bylaws forbi
ant to work, it's hard to test the upgrade process.
- Si
From: Chip Childers
Sent: Thursday, November 14, 2013 9:40 AM
To: dev@cloudstack.apache.org
Cc: Abhinandan Prateek; Alok Kumar Singh
Subject: Re: [ASF4.2.1] Release Notes
On Thu, Nov 14, 2013
I am almost +1 on this. If we can at least give the RC to people at
ccc. Not having a new package to show off next week is a missed
opportunity.
How about trying to close the vote on wednesday night?? If no
bylaws forbid it. We will then be releasing ACS while release notes
are still dripping
On Thu, Nov 14, 2013 at 09:42:11AM -0500, Sebastien Goasguen wrote:
> Anyway we can wait next week to release.
>
> quite a few of us will be together in Amsterdam, we can dedicate a hackathon
> session to 4.2.1 , make sure RN are good, upgrade path etc…then test….
>
> I'd recommend keeping the v
dhika Puthiyetath
wrote:
> Hi,
>
> The master has the most up-to-date RN for 4.2.1.
>
> From: Abhinandan Prateek
> Sent: Thursday, November 14, 2013 2:22 PM
> To: CloudStack Dev
> Cc: Radhika Puthiyetath
> Subject: Re: [ASF4.2.1] Release Notes
>
>
> It seems
Hi,
The master has the most up-to-date RN for 4.2.1.
From: Abhinandan Prateek
Sent: Thursday, November 14, 2013 2:22 PM
To: CloudStack Dev
Cc: Radhika Puthiyetath
Subject: Re: [ASF4.2.1] Release Notes
It seems the upgrade section of release notes will require a review, probably
followed by a
It seems the upgrade section of release notes will require a review, probably
followed by a revamp (?).
Can we have some volunteers who are familiar with various upgrade paths comment
on it ?
Me and Radhika will try to consolidate those comments, snippets and fix the RN
for 4.2.1.
-abhi
RN fo
35 matches
Mail list logo
