See <http://jenkins.buildacloud.org/job/cloudstack-4.3-forward-maven-build/184/>
--
Started by an SCM change
[EnvInject] - Loading node environment variables.
Building remotely on cloudstack-buildslave-centos6-83b
(cloudstack-buildslave-cento
See <http://jenkins.buildacloud.org/job/cloudstack-4.3-forward-maven-build/183/>
--
Started by an SCM change
[EnvInject] - Loading node environment variables.
Building remotely on cloudstack-buildslave-centos6-83b
(cloudstack-buildslave-cento
See <http://jenkins.buildacloud.org/job/cloudstack-4.3-forward-maven-build/182/>
--
Started by an SCM change
[EnvInject] - Loading node environment variables.
Building remotely on cloudstack-buildslave-centos6-83b
(cloudstack-buildslave-cento
See <http://jenkins.buildacloud.org/job/cloudstack-4.3-forward-maven-build/181/>
--
Started by an SCM change
[EnvInject] - Loading node environment variables.
Building remotely on cloudstack-buildslave-centos6-83b
(cloudstack-buildslave-cento
See <http://jenkins.buildacloud.org/job/cloudstack-4.3-forward-maven-build/180/>
--
Started by an SCM change
[EnvInject] - Loading node environment variables.
Building remotely on cloudstack-buildslave-centos6-e0d
(cloudstack-buildslave-cento
See <http://jenkins.buildacloud.org/job/cloudstack-4.3-forward-maven-build/179/>
--
Started by an SCM change
[EnvInject] - Loading node environment variables.
Building remotely on cloudstack-buildslave-centos6-e0d
(cloudstack-buildslave-cento
See <http://jenkins.buildacloud.org/job/cloudstack-4.3-forward-maven-build/178/>
--
Started by an SCM change
[EnvInject] - Loading node environment variables.
Building remotely on cloudstack-buildslave-centos6-e0d
(cloudstack-buildslave-cento
See <http://jenkins.buildacloud.org/job/cloudstack-4.3-forward-maven-build/177/>
--
Started by an SCM change
[EnvInject] - Loading node environment variables.
Building remotely on cloudstack-buildslave-centos6-e0d
(cloudstack-buildslave-cento
See <http://jenkins.buildacloud.org/job/cloudstack-4.3-forward-maven-build/176/>
--
Started by an SCM change
[EnvInject] - Loading node environment variables.
Building remotely on cloudstack-buildslave-centos6-e0d
(cloudstack-buildslave-cento
See <http://jenkins.buildacloud.org/job/cloudstack-4.3-forward-maven-build/175/>
--
Started by an SCM change
[EnvInject] - Loading node environment variables.
Building remotely on cloudstack-buildslave-centos6-e0d
(cloudstack-buildslave-cento
See <http://jenkins.buildacloud.org/job/cloudstack-4.3-forward-maven-build/174/>
--
Started by an SCM change
[EnvInject] - Loading node environment variables.
Building remotely on cloudstack-buildslave-centos6-e0d
(cloudstack-buildslave-cento
See <http://jenkins.buildacloud.org/job/cloudstack-4.3-forward-maven-build/173/>
--
Started by an SCM change
[EnvInject] - Loading node environment variables.
Building remotely on cloudstack-buildslave-centos6-e0d
(cloudstack-buildslave-cento
See <http://jenkins.buildacloud.org/job/cloudstack-4.3-forward-maven-build/172/>
--
Started by an SCM change
[EnvInject] - Loading node environment variables.
Building remotely on cloudstack-buildslave-centos6-e0d
(cloudstack-buildslave-cento
See <http://jenkins.buildacloud.org/job/cloudstack-4.3-forward-maven-build/171/>
--
Started by an SCM change
[EnvInject] - Loading node environment variables.
Building remotely on cloudstack-buildslave-centos6-e0d
(cloudstack-buildslave-cento
See <http://jenkins.buildacloud.org/job/cloudstack-4.3-forward-maven-build/170/>
--
Started by an SCM change
[EnvInject] - Loading node environment variables.
Building remotely on cloudstack-buildslave-centos6-e0d
(cloudstack-buildslave-cento
See <http://jenkins.buildacloud.org/job/cloudstack-4.3-forward-maven-build/169/>
--
Started by an SCM change
[EnvInject] - Loading node environment variables.
Building remotely on cloudstack-buildslave-centos6-e0d
(cloudstack-buildslave-cento
See <http://jenkins.buildacloud.org/job/cloudstack-4.3-forward-maven-build/168/>
--
Started by an SCM change
[EnvInject] - Loading node environment variables.
Building remotely on cloudstack-buildslave-centos6-e0d
(cloudstack-buildslave-cento
See
<http://jenkins.buildacloud.org/job/cloudstack-4.3-forward-maven-build/160/changes>
See <http://jenkins.buildacloud.org/job/cloudstack-4.3-forward-maven-build/159/>
--
[...truncated 2825 lines...]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 2 resources
[INFO] Copying 3 resources
[INFO]
See
<http://jenkins.buildacloud.org/job/cloudstack-4.3-forward-maven-build/158/changes>
Changes:
[wido] CLOUDSTACK-4665: Depend on rados-java 0.1.4
[wido] CLOUDSTACK-4665: Check if a snapshot is protected before trying to
unprotect
--
[...tru
See
<http://jenkins.buildacloud.org/job/cloudstack-4.3-forward-maven-build/151/changes>
See <http://jenkins.buildacloud.org/job/cloudstack-4.3-forward-maven-build/150/>
--
Started by an SCM change
[EnvInject] - Loading node environment variables.
Building remotely on cloudstack-buildslave-centos6-609 in workspace
> -Original Message-
> From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> Sent: Friday, March 14, 2014 7:43 AM
> To: dev@cloudstack.apache.org
> Subject: Re: Differences between 4.3 and 4.3-forward
>
> Yes, and we definitely cannot just take all of 4.3.1
Yes, and we definitely cannot just take all of 4.3.1 and put it in 4.3 as
many of those changes are intended for 4.3.1 and not 4.3.
On Fri, Mar 14, 2014 at 8:40 AM, Sudha Ponnaganti <
sudha.ponnaga...@citrix.com> wrote:
> Yes - 4.3-forward is unstable branch and should be merged whi
Yes - 4.3-forward is unstable branch and should be merged while 4.3 is going
through RC. It is meant for maintenance release.
-Original Message-
From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
Sent: Friday, March 14, 2014 7:36 AM
To: dev@cloudstack.apache.org
Subject: Re
@cloudstack.apache.org
> Subject: RE: Differences between 4.3 and 4.3-forward
>
> Will these automatically go into 4.3.1, do we know if they've gone into
> master as well?
>
> Otherwise does this mean we have a load of bug fixes which we're not
> putting into 4.3.0 whic
: Differences between 4.3 and 4.3-forward
Will these automatically go into 4.3.1, do we know if they've gone into master
as well?
Otherwise does this mean we have a load of bug fixes which we're not putting
into 4.3.0 which could potentially become orphaned in the 4.3-forward branch?
(this qu
ng
> into 4.3.0 which could potentially become orphaned in the 4.3-forward branch?
> (this query may be just my ignorance regarding ACS branching)
>
> Regards,
>
> Paul Angus
> Cloud Architect
> S: +44 20 3603 0540 | M: +447711418784 | T: @CloudyAngus
> paul.an...@sh
Will these automatically go into 4.3.1, do we know if they've gone into master
as well?
Otherwise does this mean we have a load of bug fixes which we're not putting
into 4.3.0 which could potentially become orphaned in the 4.3-forward branch?
(this query may be just my ignorance reg
Hey,
There is a sizable number of differences between the two branch. Maybe it’s
time to ditch 4.3-forward and recreate it based on current 4.3?
Cheers,
Hugo
Hugos-MacBook-Pro:cloudstack hugo (4.3-forward)$ git diff --stat 4.3-forward 4.3
api/src/org/apache/cloudstack/api/command/user
See
<http://jenkins.buildacloud.org/job/cloudstack-4.3-forward-maven-build/141/changes>
See <http://jenkins.buildacloud.org/job/cloudstack-4.3-forward-maven-build/140/>
--
Started by an SCM change
[EnvInject] - Loading node environment variables.
Building remotely on cloudstack-buildslave-centos6-1d6 in workspace
See
<http://jenkins.buildacloud.org/job/cloudstack-4.3-forward-maven-build/125/changes>
4.3 and there was some change for
> java7 made to repo, during that time.
> > Note, above may not be a true solution to the below problem, but it
> worked. The local binaries are getting corrupted somehow it seems.
> >
> > Santhosh
> >
I am facing a build failure but for a different reason on 4.3-forward. Looks
like due to
commit 065ac54bd7755cb44667c71311293c8f2110b3f3
Author: tuna
Date: Sat Mar 1 11:36:27 2014 +0700
CLOUDSTACK-6162: add UI for OVS plugin
[INFO
Santhosh
From: ng.t...@gmail.com [ng.t...@gmail.com] on behalf of Nguyen Anh Tu
[t...@apache.org]
Sent: Monday, March 03, 2014 12:27 AM
To: dev@cloudstack.apache.org
Subject: RE: Build on 4.3-forward Fails: Shows Failure for Framework-Clustering
Santhosh,
mail using mobile)
I have to fix my commit yesterday to 4.3-forward branch.
--Tuna
Sent from my GT-N7000
Thanks Santhosh!
--Tuna
Sent from my GT-N7000
On Mar 3, 2014 12:27 AM, "Santhosh Edukulla"
wrote:
> Tuna,
>
> I removed the packages under ~/.m2/repository/, up
d only the problem jars from above path, but it didn't
> worked.
>
> Santhosh
>
> From: ng.t...@gmail.com [ng.t...@gmail.com] on behalf of Nguyen Anh Tu [
> t...@apache.org]
> Sent: Sunday, March 02, 2014 12:05 PM
> To: dev@clouds
l.com [ng.t...@gmail.com] on behalf of Nguyen Anh Tu
[t...@apache.org]
Sent: Sunday, March 02, 2014 12:05 PM
To: dev@cloudstack.apache.org
Subject: Re: Build on 4.3-forward Fails: Shows Failure for Framework-Clustering
Am also facing this issue too. Anyone can help?
--Tuna
On Thu, Jan 23, 2014
ku...@citrix.com]
> Sent: Thursday, January 23, 2014 1:20 PM
> To: dev@cloudstack.apache.org
> Subject: Build on 4.3-forward Fails: Shows Failure for Framework-Clustering
>
> Team,
>
> 1. We are seeing a build failure for latest 4.3-forward branch code. Below
> is the error
On 01.03.2014 23:27, Marcus wrote:
4.3-forward is where commits go that you want to eventually end up in
4.3.x, whether it be another RC build or a maintenance release
(4.3.1). Then the release manager approves and pulls into 4.3, or when
4.3 is released pulls all of 4.3-forward back into 4.3
4.3 is the branch from which I build RCs. 4.3-forward is temporary staging
branch where folks post fixes for issues. I pick up critical issues needed from
there into 4.3. Once 4.3 GAs i will merge 4.3-forward into 4.3 and delete the
forward branch.
Thanks
Animesh
On Mar 1, 2014, at 10:40 AM
4.3-forward is where commits go that you want to eventually end up in
4.3.x, whether it be another RC build or a maintenance release
(4.3.1). Then the release manager approves and pulls into 4.3, or when
4.3 is released pulls all of 4.3-forward back into 4.3 for the next
release going forard.
On
Hi,
What's the difference between 4.3 and 4.3-forward. From which will the
official 4.3 release be build?
Lucian
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro
See <http://jenkins.buildacloud.org/job/cloudstack-4.3-forward-maven-build/124/>
--
[...truncated 410 lines...]
[INFO] Nullcheck of sc at line 432 of value previously dereferenced in
com.cloud.utils.db.GenericDaoBase.customSearchIncludingR
See
<http://jenkins.buildacloud.org/job/cloudstack-4.3-forward-maven-build/123/changes>
Changes:
[ng.tuna] CLOUDSTACK-6162: add UI for OVS plugin
--
[...truncated 18680 lines...]
[INFO] --- maven-resources-plugin:2.5:testResources (default-testRes
On Feb 26, 2014, at 1:31 PM, John Kinsella wrote:
> Before we go to another vote - apidocs build is failing with:
>
> Traceback (most recent call last):
> File "/home/jlk/code/cloudstack/tools/apidoc/gen_toc.py", line 195, in
>
>category = choose_category(fn)
> File "/home/jlk/code/clou
Before we go to another vote - apidocs build is failing with:
Traceback (most recent call last):
File "/home/jlk/code/cloudstack/tools/apidoc/gen_toc.py", line 195, in
category = choose_category(fn)
File "/home/jlk/code/cloudstack/tools/apidoc/gen_toc.py", line 175, in
choose_category
Ah :) That makes sense then.
On Tue, Feb 25, 2014 at 5:38 PM, Animesh Chaturvedi <
animesh.chaturv...@citrix.com> wrote:
>
> He meant the other way.
>
>
> Thanks
> Animesh
>
--
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkow...@solidfire.com
o: 303.746.7302
Adva
He meant the other way.
Thanks
Animesh
Just curious about cherry picking here. I was under the impression we only
send requests to cherry pick from, say, 4.3-forward to 4.3 and that going
from 4.3 to 4.3-forward does not require such a request.
On Tue, Feb 25, 2014 at 3:04 PM, Frank Zhang wrote:
> com
commit 20efa0c8a6b83c6590eab48fefac81b72b2082a9
Author: Frank.Zhang
Date: Mon Feb 24 13:30:24 2014 -0800
CLOUDSTACK-6155
Baremetal agent RPM missing in spec file
commit c1806bd873fe661756aeee94b25339c25f9724a5
Author: Frank.Zhang
Date: Fri Feb 21 13:22:55 2014 -0800
CLOUDSTACK-
On Mon, Feb 3, 2014 at 7:55 AM, Rajani Karuturi
wrote:
> you please do it on 4.3-forward and master as well.
I'll do it on 4.3-forward and I'll be on all findbugs issues on master
so it'll pass by automatically
Hi Daan/Ian,
looks like the change is only in 4.3. Can you please do it on 4.3-forward and
master as well.
Thanks,
~Rajani
On 03-Feb-2014, at 12:21 am, Daan Hoogland wrote:
> just pushed :(
>
>
> On Sun, Feb 2, 2014 at 7:50 PM, Ian Duffy wrote:
>> Daan,
>>
&
, 2014 at 6:52 PM, Rajani Karuturi
>> wrote:
>> > Sure Daan. Will submit a review request for master and 4.3-forward
>> tomorrow morning IST.
>> >
>> > Thanks,
>> > ~Rajani
>> >
>> >
>> >
>> > On 02-Feb-2014, at 8:17
Daan,
Have this done already, just about to push.
On 2 February 2014 18:47, Daan Hoogland wrote:
> never mind, I thought you are committer. I'll fix
>
> On Sun, Feb 2, 2014 at 6:52 PM, Rajani Karuturi
> wrote:
> > Sure Daan. Will submit a review request for master and
never mind, I thought you are committer. I'll fix
On Sun, Feb 2, 2014 at 6:52 PM, Rajani Karuturi
wrote:
> Sure Daan. Will submit a review request for master and 4.3-forward tomorrow
> morning IST.
>
> Thanks,
> ~Rajani
>
>
>
> On 02-Feb-2014, at 8:17 pm, Daan H
Sure Daan. Will submit a review request for master and 4.3-forward tomorrow
morning IST.
Thanks,
~Rajani
On 02-Feb-2014, at 8:17 pm, Daan Hoogland wrote:
> On Sun, Feb 2, 2014 at 12:48 PM, Rajani Karuturi
> wrote:
>> what we should use is new String(bytes[])
>
>
>
On Sun, Feb 2, 2014 at 12:48 PM, Rajani Karuturi
wrote:
> what we should use is new String(bytes[])
ok, makes sense. Can you revert my commit and make a new patch?
thanks,
Daan
ommand/LdapCreateAccountCmd.java
and in all the branches master, 4.3-forward, 4.3
regarding the encoding issue, The initial version wasn’t storing the random
string directly in db but a base64 encoded one(at least it was trying to do
that and had a bug). For example, abcdef would become YWJjZGVm. With th
imesh,
>>>>>>>>>
>>>>>>>>> Tested all those changes to detail. Those lines were removed due to
>>>>>>>>> unexpected behavior that I had not spotted until now.
>>>>>>>>>
>>>>>>>>&
t; >> if a
> >>>>>>> users password was reset in LDAP the old password was still
> allowing
> >> login
> >>>>>>> for a limited time.
> >>>>>>>
> >>>>>>> Please pull the changes
t;>>>>> for a limited time.
>>>>>>>
>>>>>>> Please pull the changes forward,
>>>>>>> Thanks
>>>>>>>
>>>>>>> Ian.
>>>>>>> On 29 Jan 2014 00:07, "Animesh Chaturvedi" <
t;>>>> wrote:
> >>>>>
> >>>>>> If I look at this commit for example
> >>>>>>
> >>>>>>
> >>>>>>
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit
t;>>> environment.put("com.sun.jndi.ldap.connect.pool", "true");
>>>>>>
>>>>>> Is that reported by find bug? I don't know this code so not sure if it
>>>>>> is
>>>>>> int
t;
>>>>> It removes the two lines from LdapContextFactory.java
>>>>>
>>>>> environment.put("com.sun.jndi.ldap.read.timeout", "500");-
>>>>> environment.put("com.sun.jndi.ldap.connect.pool", "true")
ut("com.sun.jndi.ldap.connect.pool", "true");
>>>>
>>>> Is that reported by find bug? I don't know this code so not sure if it is
>>>> intentional or not ?
>>>>
>>>> The point is there may be unintended risks in allowi
by find bug? I don’t know this code so not sure if it is
>>> intentional or not ?
>>>
>>> The point is there may be unintended risks in allowing late changes.
>>>
>>>
>>>
>>> -Original Message-
>>> From: Ani
-Original Message-
From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
Sent: Wednesday, January 29, 2014 1:06 PM
To: dev; Animesh Chaturvedi
Subject: Re: Findbugs report on 4.3-forward
H Animesh,
I am done cherry-picking, compiling and pushing.
[Animesh] Cool, I will also need to
H Animesh,
I am done cherry-picking, compiling and pushing.
I wonder if now is opportune to build a new rc. shouldn't we wait till
more people have tested? I for instance (doing a quarter of the test
plans that we have at Schuberg Philis) ran into some issues and am not
sure yet if they are in th
On Wed, Jan 29, 2014 at 9:50 PM, Daan Hoogland wrote:
> and will the push
and will then push
On Wed, Jan 29, 2014 at 9:36 PM, Animesh Chaturvedi
wrote:
> [Animesh] I know but at this time we need closer scrutiny and just the
> specific change helps in that. There was a similar comment in private when
> some of us were reviewing security patches.
point taken
I am not cherry picking the
-Original Message-
From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
Sent: Wednesday, January 29, 2014 12:14 PM
To: dev
Subject: Re: Findbugs report on 4.3-forward
On Wed, Jan 29, 2014 at 8:48 PM, Animesh Chaturvedi
wrote:
> Instant gratification on fixing something is trump
nesday, January 29, 2014 8:47 AM
> To: dev
> Subject: Re: Findbugs report on 4.3-forward
>
> The first five I allready posted. The ones between brackets seem minor to me.
> Then again they also pose the least risk so in my opinion you should pull
> them all. The last one is a bug
On Wed, Jan 29, 2014 at 8:48 PM, Animesh Chaturvedi
wrote:
> Instant gratification on fixing something is trumping managing risk.
I don't think I like the implication of that remark. I am sure you
mean well and are tired.
> The patches are littered with formatting changes that make review
> time
good point Mike,
I would like to add that in our case 'quality' means 'usability'. We
are not writing military or madical grade code. However I don't want
to tell a big far eastern telco that their it is out because i left an
== in the code that was meant to be an equals() call, or a leak
because
build another RC today.
Animesh
-Original Message-
From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
Sent: Wednesday, January 29, 2014 8:47 AM
To: dev
Subject: Re: Findbugs report on 4.3-forward
The first five I allready posted. The ones between brackets seem minor to me.
Then again
-Original Message-
From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
Sent: Wednesday, January 29, 2014 11:15 AM
To: dev@cloudstack.apache.org
Subject: Re: Findbugs report on 4.3-forward
I agree that quality should be our primary focus.
[Animesh] No one would disagree that
I agree that quality should be our primary focus. My one point of caution
here would be, "How risky are these fixes?"
Just because we believe we have fixes for issues does not necessarily mean
they should be put in a release late in the game. We have to weigh the
benefits of having the fixes versu
On Tue, Jan 28, 2014 at 11:36:52PM +0100, Hugo Trippaers wrote:
> Hey Animesh,
>
> Not in agreement here. These are squashed bugs and we want as less bugs in
> the release as possible.
>
> This is why we test any RC before we release it. I say include all the big
> fixes we have in the release.
please pull d38a50343130f6f147e2c9c7b2e32a43f31c7e6b to 4.3
this one came out of our regression testing, I hope other people are
keeping up the testing as well in spite of all the discussion on the
RC!!!
thanks for your patience Animesh,
Daan
On Wed, Jan 29, 2014 at 5:55 PM, Daan Hoogland wrote
See
<http://jenkins.buildacloud.org/job/cloudstack-4.3-forward-maven-build/33/changes>
On Wed, Jan 29, 2014 at 5:47 PM, Daan Hoogland wrote:
> and
>
> caf17c2f46bf317ec8966b08aaff728a73fda14a
never mind that last one, i was in a hury and screwed up. will revert
See
<http://jenkins.buildacloud.org/job/cloudstack-4.3-forward-maven-build/32/changes>
Changes:
[Daan Hoogland] CLOUDSTACK-5979 vlan parsing fixed
--
[...truncated 3436 lines...]
d local vars. This doesn't seem vital
>>> (or dangerous) but pulling only one seems very few.
>>>
>>>
>>> On Wed, Jan 29, 2014 at 7:11 AM, Animesh Chaturvedi
>>> wrote:
>>>>
>>>>
>>>> -Original Message-
>>
gt;>>
>>> -Original Message-
>>> From: Ian Duffy [mailto:i...@ianduffy.ie]
>>> Sent: Tuesday, January 28, 2014 6:34 PM
>>> To: CloudStack Dev
>>> Subject: RE: Findbugs report on 4.3-forward
>>>
>>> Hi Animesh,
>>>
, Animesh Chaturvedi
> wrote:
>>
>>
>> -Original Message-
>> From: Ian Duffy [mailto:i...@ianduffy.ie]
>> Sent: Tuesday, January 28, 2014 6:34 PM
>> To: CloudStack Dev
>> Subject: RE: Findbugs report on 4.3-forward
>>
>> Hi Animesh,
>>
-
> From: Ian Duffy [mailto:i...@ianduffy.ie]
> Sent: Tuesday, January 28, 2014 6:34 PM
> To: CloudStack Dev
> Subject: RE: Findbugs report on 4.3-forward
>
> Hi Animesh,
>
> Tested all those changes to detail. Those lines were removed due to
> unexpected behavior that I had not
-Original Message-
From: Ian Duffy [mailto:i...@ianduffy.ie]
Sent: Tuesday, January 28, 2014 6:34 PM
To: CloudStack Dev
Subject: RE: Findbugs report on 4.3-forward
Hi Animesh,
Tested all those changes to detail. Those lines were removed due to unexpected
behavior that I had not
A quick look at 20+ commits from
>> Daan show many formatting changes that may not be necessary and hinder
>> quick review.
>>
>> -Original Message-
>> From: Hugo Trippaers [mailto:trip...@gmail.com]
>> Sent: Tuesday, January 28, 2014 3:16 PM
>>
m]
> Sent: Tuesday, January 28, 2014 3:35 PM
> To: dev@cloudstack.apache.org
> Subject: RE: Findbugs report on 4.3-forward
>
> Are you sure all of the ones are needed. A quick look at 20+ commits from
> Daan show many formatting changes that may not be necessary and hinder
> qu
imesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
Sent: Tuesday, January 28, 2014 3:35 PM
To: dev@cloudstack.apache.org
Subject: RE: Findbugs report on 4.3-forward
Are you sure all of the ones are needed. A quick look at 20+ commits from Daan
show many formatting changes that may not be necessary
@cloudstack.apache.org
Subject: Re: Findbugs report on 4.3-forward
Sent from my iPhone
> On 28 jan. 2014, at 23:50, Animesh Chaturvedi
> wrote:
>
>
> -Original Message-
> From: Hugo Trippaers [mailto:trip...@gmail.com]
> Sent: Tuesday, January 28, 2014 2:37 PM
> To: dev@cl
Koushik,
I just tested in 4.3-forward branch.
This is an API bug, not UI bug.
(1) "virtualmachine" object returned by deployVirtualMachine API,
queryAsyncJobResult API does NOT include name, displayname, zonename, state
property.
http://10.215.3.26:8080/client/a
org
> Subject: Re: Findbugs report on 4.3-forward
>
> Hey Animesh,
>
> Not in agreement here. These are squashed bugs and we want as less bugs in
> the release as possible.
> [Animesh] I understand but once we enter RC phase we only limit important
> fixes. I have pu
-Original Message-
From: Hugo Trippaers [mailto:trip...@gmail.com]
Sent: Tuesday, January 28, 2014 2:37 PM
To: dev@cloudstack.apache.org
Cc: dev@cloudstack.apache.org
Subject: Re: Findbugs report on 4.3-forward
Hey Animesh,
Not in agreement here. These are squashed bugs and we want as
h he called -1.
>
> Thanks
> Animesh
>
> -Original Message-
> From: Trippie [mailto:trip...@gmail.com] On Behalf Of Hugo Trippaers
> Sent: Tuesday, January 28, 2014 1:29 AM
> To: dev
> Subject: Re: Findbugs report on 4.3-forward
>
> Hey Animesh,
>
> I
Of Hugo Trippaers
> Sent: Tuesday, January 28, 2014 1:29 AM
> To: dev
> Subject: Re: Findbugs report on 4.3-forward
>
> Hey Animesh,
>
> I agree with Daan here. We focussed on the bugs with a findbugs annotation of
> scariest. I think that would warrant them to be includ
Hugo's commit for which he called -1.
Thanks
Animesh
-Original Message-
From: Trippie [mailto:trip...@gmail.com] On Behalf Of Hugo Trippaers
Sent: Tuesday, January 28, 2014 1:29 AM
To: dev
Subject: Re: Findbugs report on 4.3-forward
Hey Animesh,
I agree with Daan here. We focussed o
less secure than the previous one.
Thanks,
~Rajani
On 28-Jan-2014, at 10:55 am, Ian Duffy
mailto:i...@ianduffy.ie>> wrote:
Hi Animesh,
Can you cherry-pick the below commit from from 4.3-forward to 4.3 branch?
Fix findbug issues within LDAP authenticator
commit 92b4f66d73562e4211d2d7
1 - 100 of 136 matches
Mail list logo
