sorry for the late reply, Paul. I am sick t home at the moment. Better then
yesterday though, thanks;)
I had a rule that blockers are only that if they have been discussed as
such on list
I was unaware new 'blocker' were introduced and didn't look at those yet.
In principle these are critical
Hi Daan,
What's your view on these 'blockers' for the 4.4.2 release?
https://issues.apache.org/jira/issues/?jql=project%20%3D%20CLOUDSTACK%20AND%20priority%20%3D%20Blocker%20AND%20resolution%20%3D%20Unresolved%20AND%20affectedVersion%20%3D%204.4.2%20ORDER%20BY%20key%20DESC
CLOUDSTACK-8210
...@shapeblue.commailto:paul.an...@shapeblue.com
From: Funs Kessen [mailto:fozzielumpk...@gmail.com] On Behalf Of Funs Kessen
Sent: 13 March 2015 13:26
To: Paul Angus
Cc: dev@cloudstack.apache.org
Subject: Re: Jira Housekeeping - 'Old Blockers'
Hey Paul,
OVM and OVM3 have nothing to do with each
:* 13 March 2015 13:26
*To:* Paul Angus
*Cc:* dev@cloudstack.apache.org
javascript:_e(%7B%7D,'cvml','dev@cloudstack.apache.org');
*Subject:* Re: Jira Housekeeping - 'Old Blockers'
Hey Paul,
OVM and OVM3 have nothing to do with each other, they are completely
separated code wise
Hey All,
Does anyone know if this bug:
https://issues.apache.org/jira/browse/CLOUDSTACK-5211 (Need Support for the OVM
for the Report sockets cloudstack-4908)
is fixed in the work which has been done for OVM3 ?
Regards,
Paul Angus
Cloud Architect
[cid:image001.png@01CFD9AB.6EFF8BF0]
S: +44
Hey Paul,
OVM and OVM3 have nothing to do with each other, they are completely separated
code wise. The stats collection in OVM3 is done via the cloudstack plugin in
the agent rather than native via the agent report socket. In Ovm3.2 and Ovm 3.3
the implementation also differs as 3.3 supports
To: dev@cloudstack.apache.org
Subject: Re: Jira Housekeeping - 'Old Blockers'
Paul,
I do see my name beside some of these :S I believe it's fair to downgrade mine
to something lower and/or close them. However, I am pretty sure these bugs
still exists today, but unfortunately I'm not equipped
Cloud Architect
S: +44 20 3603 0540 | M: +447711418784 | T: CloudyAngus
paul.an...@shapeblue.com
-Original Message-
From: Francois Gaudreault [mailto:fgaudrea...@cloudops.com]
Sent: 12 March 2015 03:49
To: dev@cloudstack.apache.org
Subject: Re: Jira Housekeeping - 'Old Blockers'
Paul
'.
Regards
Paul Angus
Cloud Architect
S: +44 20 3603 0540 | M: +447711418784 | T: CloudyAngus
paul.an...@shapeblue.com
-Original Message-
From: Rajani Karuturi [mailto:raj...@apache.org]
Sent: 08 March 2015 10:50
To: dev@cloudstack.apache.org
Subject: Re: Jira Housekeeping - 'Old Blockers'
I
: +447711418784 | T: CloudyAngus
paul.an...@shapeblue.com
-Original Message-
From: Rajani Karuturi [mailto:raj...@apache.org]
Sent: 08 March 2015 10:50
To: dev@cloudstack.apache.org
Subject: Re: Jira Housekeeping - 'Old Blockers'
I would like to share a blog post I read recently which I believe
-Original Message-
From: Erik Weber [mailto:terbol...@gmail.com]
Sent: 08 March 2015 19:14
To: dev
Subject: Re: Jira Housekeeping - 'Old Blockers'
On Sun, Mar 8, 2015 at 11:50 AM, Rajani Karuturi raj...@apache.org wrote:
I would like to share a blog post I read recently which I
On Sun, Mar 8, 2015 at 11:50 AM, Rajani Karuturi raj...@apache.org wrote:
I would like to share a blog post I read recently which I believe is
relevant in this context.
http://words.steveklabnik.com/how-to-be-an-open-source-gardener
I like the 'stale' part
--
Erik
I would like to share a blog post I read recently which I believe is
relevant in this context.
http://words.steveklabnik.com/how-to-be-an-open-source-gardener
~Rajani
On Sat, Mar 7, 2015 at 11:18 PM, Daan Hoogland daan.hoogl...@gmail.com
wrote:
Guys, It has been discussed before and My
Guys, It has been discussed before and My proposal was that no issue
is a blocker unless it has been discussed as such on dev@. This has
never been voted on AFAIR. No release should go out with a blocker
open, so 'old' blockers is kind of awkward. I'd say triage them and
close or downgrade.
On
Hi Paul,
This is a good initiative !
I think we should clean up Jira as we go forward. Blockers languishing around
is not a good sign.
I personally feel that blockers that are more than a year old can be safely
closed, as these may be hard to reproduce as things have changed since then or
15 matches
Mail list logo
