Ok so we are good. Looking forward to VOTE thread
> -Original Message-
> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
> Sent: Tuesday, July 01, 2014 12:56 PM
> To: dev
> Subject: Re: [ACS4.4] RC1
>
> thats the one,
>
> On Tue, Jul 1, 2014 at 8:16 PM,
ong.
>
>
> Animesh
>
>
>> -Original Message-
>> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
>> Sent: Tuesday, July 01, 2014 5:05 AM
>> To: dev
>> Subject: Re: [ACS4.4] RC1
>>
>> Animesh,
>>
>> Do you send this
> Sent: Tuesday, July 01, 2014 5:05 AM
> To: dev
> Subject: Re: [ACS4.4] RC1
>
> Animesh,
>
> Do you send this as a counter proposal or overriding the procedure on the
> wiki? That is the one I am following.
>
> On Mon, Jun 30, 2014 at 9:56 PM, Animesh Chaturvedi
>
gt;
>
> Regards,
> Rayees
>
>
> -Original Message-
> From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
> Sent: Monday, June 30, 2014 12:56 PM
> To: dev@cloudstack.apache.org
> Subject: RE: [ACS4.4] RC1
>
> Daan
>
> We have been followi
>
> [1] http://markmail.org/message/ksyv4gftcsjc4pma
>
> Thanks
> Animesh
>
>> -Original Message-
>> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
>> Sent: Monday, June 30, 2014 2:23 AM
>> To: dev
>> Subject: [ACS4.4] RC1
>>
>&g
DSTACK-7011
https://issues.apache.org/jira/browse/CLOUDSTACK-7012
Regards,
Rayees
-Original Message-
From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
Sent: Monday, June 30, 2014 12:56 PM
To: dev@cloudstack.apache.org
Subject: RE: [ACS4.4] RC1
Daan
We have been following the convent
> To: dev
> Subject: [ACS4.4] RC1
>
> This is going to be the vote thread but I read back the procedure and found
> that I should more explicitly ask for consent before starting the vote.
>
> 162ea957e6f02e56f2de7a639f4c7e593b1b3e72 is the commit id for the
> version I would like t
thanks Ove,
running
$ mvn clean
$ mvn test
no errors
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 05:59 min
[INFO] Finished at: 2014-06-30T21:12:00+01:00
On Mon, Jun 30, 2014 at 9:03 PM, Ove Ewerlid wrote:
> On 06/30/201
On 06/30/2014 06:02 PM, Daan Hoogland wrote:
499ff73f1a14bddd81c5788930c43b2a3de099ed is the one that has the
checkstyle pom edited as well. It is on branch 4.4-RC20140630T1754.
This time I ran mvn clean test *after* running build_asf.sh threw it
away and ran the script again. Hopefully it will b
499ff73f1a14bddd81c5788930c43b2a3de099ed is the one that has the
checkstyle pom edited as well. It is on branch 4.4-RC20140630T1754.
This time I ran mvn clean test *after* running build_asf.sh threw it
away and ran the script again. Hopefully it will be alright now.
Please proof me wrong, I dare yo
On 06/30/2014 02:51 PM, Daan Hoogland wrote:
Ove, to be sure I got you: Does your script need to have the branch
checked out when building a version by tag or commit-id or does it
checkout the version and then build it?
The script is setup for the historical ACS method of using a specific
comm
Ove, to be sure I got you: Does your script need to have the branch
checked out when building a version by tag or commit-id or does it
checkout the version and then build it?
The commit id is not on the branch 4.4 but on a branch of that called
4.4-RCT
But I noticed that you are right, the pom fo
On 06/30/2014 11:23 AM, Daan Hoogland wrote:
This is going to be the vote thread but I read back the procedure and
found that I should more explicitly ask for consent before starting
the vote.
162ea957e6f02e56f2de7a639f4c7e593b1b3e72 is the commit id for the
version I would like to release. Do w
This is going to be the vote thread but I read back the procedure and
found that I should more explicitly ask for consent before starting
the vote.
162ea957e6f02e56f2de7a639f4c7e593b1b3e72 is the commit id for the
version I would like to release. Do we have the feeling that this is a
version stabl
14 matches
Mail list logo
