Hi,
We did some preliminary validation with ACS 4.5 and XS 6.5 (Beta release
versions) in our labs and it is working fine with no blocker issues.
Besides the features listed by Stephen below, some additional guest OS are
introduced in this release.
Thanks
/Sudha
-Original Message-
F
Why not address CI and Quality standards that came up in the discussions and
get them out of the way first and then address gitflow as a second step. Looks
like majority consensus is in that direction. Now CI is available, seem to be
easy to implement as proposal has been done by Alex. Looks lik
+1
Also each check in (defect or new feature) should be accompanied by CI based
tests as unit tests ( JUNIT tests) seem to be not so popular with CS community.
Discussions seem to be moving towards this. But some sort of enforcement is
needed at this point. Community has tried all else for p
+1
On Thu, Jul 31, 2014 at 12:28 PM, Rajani Karuturi
wrote:
> Hi All,
>
> We had long discussions on the git flow.
> I tried to capture the summary of it @
> http://markmail.org/message/j5z7dxjcqxfkfhpj
> This is updated on wiki @
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Git#Gi
+1 to use same version number for Marvin package as Cloudstack release.
-Original Message-
From: Rohit Yadav [mailto:rohit.ya...@shapeblue.com]
Sent: Monday, July 28, 2014 5:34 AM
To: dev@cloudstack.apache.org
Cc: Prasanna Santhanam
Subject: Re: Marvin Package?
Hi Hugo,
Does it make sen
Ritu,
Would be good to add automated tests for the procedure you have outlined.
Marvin has already similar tests and you should be able to reuse them.
Thanks
/sudha
>> Testing
>> ---
>>
>> *Create an isolated network; verify that the port-profile is created on
>> the Brocade switch.
,
Santhosh
____
From: Sudha Ponnaganti [sudha.ponnaga...@citrix.com]
Sent: Monday, July 21, 2014 7:42 AM
To: dev@cloudstack.apache.org
Subject: RE: Disabling failed test cases (was RE: Review Request 23605:
CLOUDSTACK-7107: Disabling failed test cases)
Hugo,
I absolutely agree with you that te
the meantime.
Doing so is too confusing, we need to be able to rely on the fact that if the
tests report OK everything is actually OK.
Cheers,
Hugo
On 21 jul. 2014, at 12:28, Sudha Ponnaganti wrote:
> In the beginning to get CI up and running, it would be ok to disable these
> hand
In the beginning to get CI up and running, it would be ok to disable these
handful of tests while getting fixes in, to achieve 100% pass rates. When CI
runs in production, code changes need to be reverted if there are any "new"
failures to keep CI pass rates at 100% (a known state to make CI
Mike / Hieu,
Thank you for your consideration. Even if it is not needed at the review time,
can Marvin tests ( if applicable, simulator tests) can be added before you
close on the feature. That would help to run regression tests on this feature
for all releases.
Some sort of automated tests (
Hi Carlos,
Were you able to resolve the following? Was your upgrade successful?
Thanks
/sudha
-Original Message-
From: Carlos Reátegui [mailto:create...@gmail.com]
Sent: Friday, June 27, 2014 8:55 PM
To: CloudStack-Users
Cc: dev@cloudstack.apache.org
Subject: 4.4 upgrade issues
I am tr
future bug fix releases...
-sebastien
> and
> author would ask for pick up in that case. I think that's what's
> happened with 4.3-forward branch.
>
> --Sheng
>
>
> On Sat, Jun 7, 2014 at 3:05 PM, Sudha Ponnaganti <
> sudha.ponnaga...@citrix.com> wr
+1
-Original Message-
From: John Kinsella [mailto:j...@stratosec.co]
Sent: Friday, June 06, 2014 7:28 PM
To: dev@cloudstack.apache.org
Subject: Re: [DISCUSS] Introducing Gerrit for quality? was: [PROPOSAL] Using
continuous integration to maintain our code quality...
+1 seems like a good
Wondering why not baseline with 4.4-forward branch.
-Original Message-
From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
Sent: Saturday, June 07, 2014 2:53 AM
To: dev
Subject: [ACS44] 112 unpicked cherries in 4.4-forward. why?
H,
To start with my personal finger pointing: especially
That is better. Hope new ones can be fixed each week while the old ones can be
prioritized based on high density.
Original message
From: Rajani Karuturi
Date:06/06/2014 6:37 AM (GMT-08:00)
To: dev@cloudstack.apache.org
Subject: Re: New Defects reported by Coverity Scan for cloud
Daan,
- 1 on releasing with blockers
- We have to get these fixed. People doesn’t get to blockers doesn’t make
severity any less.
- Also I did not see any upgrade validation done in community. Would be good if
someone confirms that they have done it already.
- Do you know if anyone is runni
udha
From: Sudha Ponnaganti
Sent: Wednesday, May 28, 2014 1:59 PM
To: dev@cloudstack.apache.org
Subject: [ACS 4.4] Blocker and Critical Defects 5/28
There are 10 blockers ( 2 more than yesterday) and 78 ( 1more than yesterday)
critical defects outstanding.
2 unassigned defects need to be triaged t
disabled IAM feature on 4.4. I have updated
the bug to retest with latest code.
Thanks
-min
On 5/27/14 3:21 PM, "Sudha Ponnaganti" wrote:
>There are 8 blockers and 77 critical defects outstanding Dashboard
>https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12323
ction param value passed
incorrectly Jessica Wang
CLOUDSTACK-6599 Template/Volume URLs expiration functionality not
working Nitin Mehta
From: Sudha Ponnaganti
Sent: Tuesday, May 27, 2014 3:21 PM
To: dev@cloudstack.apache.org
Subject: [ACS 4.4] Blocker and Critical Defects
There are 8 blockers and 77 critical defects outstanding
Dashboard
https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12323265
Blocker Defect List:
KeySummary Assignee
CLOUDSTACK-6779 [OVS] Expunging VM (deleting vif) deletes all the
rules from ovs br
-1 on the proposal to lower priority of defects based on timeframe. These are
blockers for features and some for release as well. We should not be
modifying the priority of defect unless the original reporter or RM agrees to
do so for technical reasons but not because these are not touched by
Hi,
Not able to assign tickets in JIRA. Has any policy changed??
Otherwise will log a ticket for Infra
Thanks
/Sudha
Team,
I see discussion around RC and readiness aspect from a few folks. Wanted to
update dev mailing list on what has been done that I know of from QA
standpoint. Also request other QA or test teams to chime in if they have
covered any other aspects that they have been interested in. Based on t
Below are the blocking defects that are impacting automation runs/validation of
features for ACS 4.4. Can these be picked up by interested community members.
Couple of them are picked up by majority are in unassigned state.
Thanks
/Sudha
KeySummary Assignee
CLOUDSTACK-6232
] Windowsfication of management server
Sudha,
Have you distributed a list of items yet? I'm sorry if you have and I've missed
it.
Regards
Alex Hitchins
D: +44 1892 523 587 | S: +44 2036 030 540 | M: +44 7788 423 969
alex.hitch...@shapeblue.com
-Original Message-----
From: Sudha
Can someone provide a resolution for this issue??
https://issues.apache.org/jira/i#browse/CLOUDSTACK-6303
Act creation fails
Alex,
Glad to hear that you are interested in validation aspects for this feature. We
are also interested. Not to cover the same areas, can we share general broader
categories for validation.
Thanks
/sudha
-Original Message-
From: Alex Hitchins [mailto:alex.hitch...@shapeblue.com]
Se
-Original Message-
From: Sudha Ponnaganti [mailto:sudha.ponnaga...@citrix.com]
Sent: 28 March 2014 14:47
To: dev@cloudstack.apache.org
Cc: Daan Hoogland; Donal Lafferty
Subject: RE: [PROPOSAL][Merge] Windowsfication of management server
Alex,
Glad to hear that you are interested in validation aspects
Hi Syed,
We are interested to use this feature[1]. Wanted to check what level of
validation has been done on this feature.
Appreciate your input.
[1] https://issues.apache.org/jira/i#browse/CLOUDSTACK-4821
Thanks
/sudha
Congratulation to all the community members !
-Original Message-
From: Chip Childers [mailto:chipchild...@apache.org]
Sent: Tuesday, March 25, 2014 7:05 AM
To: annou...@cloudstack.apache.org
Subject: [ANNOUNCE] Apache CloudStack 4.3.0 Released
Announcing Apache CloudStack 4.3.0
Tue Mar
Hi,
We have been using release tags as prefixes i.e ACS43, ACS44 etc for mailing
list discussions. These days these prefixes are missing for some of the
discussions. If community can use those prefixes, it would be very helpful to
follow relevant discussions.
Thanks
/Sudha
ature -
>
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=36274178
>
>
> -Pradeep
>
>
>
>
>
> On Friday, March 14, 2014 8:13 PM, Sudha Ponnaganti <
> sudha.ponnaga...@citrix.com> wrote:
>
> Other alternative is to block further check-in
Hi,
I have copied one of the project pages from prior release for ACS 4.4[1]. Will
be posting some of the QA artifacts in QA plan section.
[1] https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=39623192
Thanks
/sudha
-Original Message-
From: Sudha Ponnaganti
Can time be given till PST EOD as many developers are also in this time zone?
If specific features are being pulled in to 4.4, we might as well cut branch a
little later where approved merge queue is cleared.
-Original Message-
From: Abhinandan Prateek [mailto:abhinandan.prat...@citri
ature tests.
On Fri, Mar 14, 2014 at 8:35 AM, Marcus wrote:
> I'm not sure what the offending ones are at the moment, and there was
> recently a feature merge that was not squashed, so it might be a
> little difficult to weed through.
>
> On Mar 14, 2014 7:45 AM, "Sudha Ponn
: Differences between 4.3 and 4.3-forward
Right, I think it's dangerous to sync 4.3.1 to 4.3 because developers might
have changes in 4.3.1 that are not yet in master.
This is not my situation personally, but I imagine some devs might be in this
state.
On Fri, Mar 14, 2014 at 8:18 AM,
Yes that is my understanding that all of these would go in to next maintenance
that is why they are staged in forward branch.
-Original Message-
From: Paul Angus [mailto:paul.an...@shapeblue.com]
Sent: Friday, March 14, 2014 1:38 AM
To: dev@cloudstack.apache.org
Subject: RE: Differences
Can the offending check-ins be reverted or master be blocked for further
check-ins till blocking issue is fixed.
Talluri is running BVTs and can that be taken as basic passing criteria to
re-enable check-ins.
-Original Message-
From: Marcus [mailto:shadow...@gmail.com]
Sent: Friday, M
+1 Radical proposition. Setting goals and exit criteria is good so project can
be executed on time with expected level of quality. This is common for most of
SDLC processes, that teams would stick to the agreed up on quality cycles and
quality plans. Because of open source nature it might b
Feature freeze and Merge criteria is not defined to change the milestone
suddenly. We can create build and call it RC but that would take another 2+
months to harden to build next RC. There are only 50 defects logged for 4.4 so
far. We are away from another 600+ defects to get acceptable RC ca
Hugo,
Is it possible to setup Project page [1] on cwiki ? I am interested to post
some of the QA artifacts there related to ACS 4.4. I can also copy one from
prior releases if that is okay.
[1] https://cwiki.apache.org/confluence/display/CLOUDSTACK/Releases+in+Progress
Thanks
/Sudha
-Orig
?
Regards
Alex Hitchins
D: +44 1892 523 587 | S: +44 2036 030 540 | M: +44 7788 423 969
alex.hitch...@shapeblue.com
-Original Message-
From: Sudha Ponnaganti [mailto:sudha.ponnaga...@citrix.com]
Sent: 11 March 2014 13:12
To: dev@cloudstack.apache.org
Subject: RE: Sorting through Jira
+1
I do this also once in a while. I close or follow up with owners to close
tickets which are already resolved/ not valid / not applicable. Will continue
to do the same if there is some time on my part to cleanup backlog.
If possible can you look in to new features also and close those as we
+1 esp changes in DB area should be notified.
DB changes should be frozen couple of weeks before RC so QA would get time to
run through tests - otherwise we would be going in circles.
BTW do you have commit id for this particular check in
Thanks
/Sudha
-Original Message-
From: Mike Tu
Every release Citrix QA team is encouraging and asking community participation
in specific areas like upgrades / specific feature validation/ defect
verification etc to promote QA culture and participation from community.
Participation has been very low. Current model may not sustain in long r
gt;>>> folks
>>>>>>>>>>> opportunity to finish up their features for new proposals
>>>>>>>>>>> that are
>>>>>> yet
>>>>>>>>>>> to come out.
>>>>>>>>&g
Hi,
I am also looking for feature freeze dates for 4.4. Can RM post those?
Thanks
/Sudha
-Original Message-
From: Alex Hitchins [mailto:alex.hitch...@shapeblue.com]
Sent: Tuesday, February 25, 2014 7:00 AM
To: dev@cloudstack.apache.org
Subject: 4.4 Feature Freeze
All,
I know the 4.3 i
+1 for pre- commit testing. Whichever tool enforces it would be good choice.
For feature check in, we ( community) require sanity tests to be submitted by
feature owners and this was followed well in 4.0 release but there is lapse in
this practice now. This would be a great if RM can enforce
VMware is noredist (non-oss) platform so it is not run just like KVM and Xen.
However some of the teams may be running it locally in their labs.
-Original Message-
From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
Sent: Tuesday, January 21, 2014 2:03 PM
To: dev@cloudstack.
13 at 6:22 AM, Sudha Ponnaganti
wrote:
> Hi All,
>
> Has anyone trying upgrades for ACS 4.3 from ACS 4.x versions ??
> 4.2 and 42.1 will be covered in our lab. Wondering if anyone else is
> trying upgrades as RC is approaching soon
>
> Thanks
> /sudha
>
> From: Sudha Po
QA has been testing with 64 bit templates in 4.3 from the beginning. Only
change requested now is to change version number which is referring to older
templates.
-Original Message-
From: David Nalley [mailto:da...@gnsa.us]
Sent: Thursday, January 16, 2014 10:35 AM
To: dev@cloudstack.a
Community Members,
Following are the defects that are resolved for ACS 4.3. As RC would be done
soon, can you make sure to validate and close these defects
Thanks
/sudha
Reporter Total
Abhinav Roy 6
Ahmad Emneina 1
Alena Prokharchyk 7
Alex Huang
Thanks Nux for confirmation. Is it okay to close this issue in JIRA ??
-Original Message-
From: Nux! [mailto:n...@li.nux.ro]
Sent: Friday, January 03, 2014 12:33 AM
To: dev@cloudstack.apache.org
Subject: RE: [VOTE] 3rd round of voting for ASF 4.2.1 RC
On 03.01.2014 07:40, Nux! wrote:
> G
Nux,
Defect 5393 [1] is not reproducible in 4.3 so that got closed. Can you open a
new one for 4.2.1 with exact problem you are having. Also looks slightly
different from 5393 issue.
Running KVM with a GlusterFS shared mount point on cloudstack-4.2-223b272,
snapshots consistently fail to be
Hi All,
Has anyone trying upgrades for ACS 4.3 from ACS 4.x versions ??
4.2 and 42.1 will be covered in our lab. Wondering if anyone else is trying
upgrades as RC is approaching soon
Thanks
/sudha
From: Sudha Ponnaganti
Sent: Sunday, October 20, 2013 3:46 PM
To: dev@cloudstack.apache.org
Hi,
I would like to add a page here [1] for some reason. May be my permissions got
reset. Can you grant me to add a page
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Test+Execution+Results+for+ACS+4.3
thanks
/sudha
Checking on 5393 and will get back shortly. Same set of tests ran before as
well during 4.2. Will check on those test results or retest to see if anything
regressed since release as lot of check ins are happening.
Thanks
/sudha
-Original Message-
From: David Nalley [mailto:da...@gnsa.u
+1 for running on separate branch before check in
-Original Message-
From: sebgoa [mailto:run...@gmail.com]
Sent: Wednesday, December 11, 2013 1:12 AM
To: Santhosh Edukulla; gir...@clogeny.com; dev@cloudstack.apache.org
Cc: Prasanna Santhanam
Subject: Marvin refactoring
Hi devs and Santo
Makes sense.
Thanks
/Sudha
-Original Message-
From: Santhosh Edukulla
Sent: Wednesday, December 11, 2013 4:33 AM
To: Sudha Ponnaganti; dev@cloudstack.apache.org
Subject: RE: Tiered Quality
1. The below snapshot only depicts numbers only for KVM run.( A sample run ).
2. We will
From: Daan Hoogland [daan.hoogl...@gmail.com]
Sent: Sunday, November 03, 2013 7:07 AM
To: dev
Subject: Re: Tiered Quality
keep us posted before breakthrough as well, please. I'm very interested.
and good hunting of course,
Daan
On Sat, Nov 2, 2013 at 2:35 PM, Sudha Ponnaganti
wrote:
>
1
Marcus Sorensen 1
Milamber1
Naoki Sakamoto 1
Parth Jagirdar1
Ron Wheeler 1
sadhu suresh 1
Saksham Srivastava 1
Sangeetha Hariharan 1
Sanjay Tripathi 1
Sowmya Krishnan1
Sudha Ponnaganti 1
Timothy Ehlers 1
ase
[2]
https://cwiki.apache.org/confluence/display/CLOUDSTACK/4.2.1+Automation+Result
From: Abhinandan Prateek
Sent: Monday, November 11, 2013 1:56 AM
To: CloudStack Dev
Cc: Raja Pullela; Sudha Ponnaganti
Subject: [ACS4.2.1] request for QA update
Sudha/Raja,
You guys have been doing a QA
,
except CLOUDSTACK-5076 will fix it today
2013/11/8 Sudha Ponnaganti
> Hi,
>
> Looks like Schuberg Philis is covering 4. 1.1 -> 4.2.1 upgrade We (
> Citrix systems) would cover 4.2 -> 4.2.1
>
> I think these two paths might be enough for this minor release. I
> think
: [ACS 421] Upgrade testing
Sudha, give us till the end of next week please. I'll report back on friday, ok?
On Fri, Nov 8, 2013 at 3:12 AM, Sudha Ponnaganti
wrote:
> Hi,
>
> Looks like Schuberg Philis is covering 4. 1.1 -> 4.2.1 upgrade We (
> Citrix systems) would cover 4.2
essage-
From: Sudha Ponnaganti
To: dev
Subject: RE: [ACS 421] Upgrade testing
Thanks Daan
-Original Message-
From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
Sent: Thursday, October 31, 2013 2:33 PM
To: dev
Subject: Re: [ACS 421] Upgrade testing
H Sudha,
We will at Schuberg Phil
That is only for Unit tests - we need to instrument code coverage for BVTs and
Regressions i.e integration tests. We are pursuing this in our lab. If we get
any break through will post it to the forum. Because of customized nature of
automation framework there are few challenges there.
___
we can free up some people to test that scenario
soon.
Daan
On Thu, Oct 31, 2013 at 3:51 AM, Sudha Ponnaganti
wrote:
> Hi All,
>
> Want to check if anyone is testing upgrades from prior versions to 4.2.1. As
> Release date is getting close, If there are gaps, would like t
Hi All,
Want to check if anyone is testing upgrades from prior versions to 4.2.1. As
Release date is getting close, If there are gaps, would like to cover some
scenarios in our lab.
Thanks
/sudha
Sudha Ponnaganti would like to recall the message, "VM snapshots".
Can you log defect in apache and target for 4.2.1
Do not specify any internal stuff in the defect or on ACS mailing lists
-Original Message-
From: Angeline Shen [mailto:angeline.s...@citrix.com]
Sent: Thursday, October 24, 2013 2:19 PM
To: Anthony Xu; Kelven Yang; Chandan Purushothama; '
Sudha Ponnaganti would like to recall the message, "VM snapshots".
2
Sanjay Tripathi 1
Sanjeev N 1
Sateesh Chodapuneedi 1
Sheng Yang 4
shweta agarwal1
Sowmya Krishnan1
Sudha Ponnaganti 1
Valery Ciareszka 1
venkata swamybabu budumuru 2
Wei Zhou 1
Grand Total
Another reminder to see if anyone is interested to cover the following topics.
Some of you are going to try upgrades and some of the features anyways so
checking to see if you would like to sign up for validation of the following
areas.
From: Sudha Ponnaganti
Sent: Tuesday, October 15, 2013 4
Hi All,
43 is getting started now and it is great opportunity to participate and
contribute towards ACS 43 Validation if you have interest in testing and
automation related areas. Below are the tasks and I have posted a task sheet to
sign up. Pl review and see if you would like to sign up. The
Hi,
I see the date to propose features has passed [1]. When would the tasks be
created to see full scope for 4.3??
[1]
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Cloudstack+4.3+Release
Thanks
/sudha
Do you mean UI guys??
-Original Message-
From: Abhinandan Prateek [mailto:abhinandan.prat...@citrix.com]
Sent: Friday, October 04, 2013 4:54 AM
To: CloudStack Dev
Cc: Brian Federle; Jessica Wang; Sonny Chhen
Subject: [ACS4.2.1] UI tickets
There are around ~72 UI tickets open. Most of th
Agree to keep tests with main repo as suggested as tests are tied to releases.
Backward compatibility of framework need to be considered when breaking it
apart as we still use the framework on older branches for validation of
patches.
-Original Message-
From: Animesh Chaturvedi [mailto
I assume changes are being done on a separate branch. We are currently going to
run automation on Master for 4.3. Just want to make sure that this would not
impact current runs.
-Original Message-
From: Sebastien Goasguen [mailto:run...@gmail.com]
Sent: Wednesday, October 02, 2013 11:2
Ilya,
I work for Citrix QA so can speak to some of the discussion that you have
raised around QA. I have expressed my opinion on assigning defects in another
thread.
-Like Animesh mentioned, Citrix QA has contributed quite a bit for ACS 4.2, I
can say as much as 90% + towards any of the QA a
+1 on multiple RMs
+1 on assigning defects by RMs as this gives faster closure on defects esp
critical ones. This can be done over IRC at regular intervals instead of
waiting for folks to claim defects which may take time given the priorities
that each one has. Same with validation as well.
+1 (binding) on donation
-Original Message-
From: Chip Childers [mailto:chipchild...@apache.org]
Sent: Wednesday, September 25, 2013 10:13 AM
To: dev@cloudstack.apache.org
Subject: [VOTE] Accept the donation of a Contrail plugin into Apache CloudStack
Hi all!
As stated in other threads,
: +447711418784 | T: CloudyAngus paul.an...@shapeblue.com
-Original Message-
From: Sudha Ponnaganti [mailto:sudha.ponnaga...@citrix.com]
Sent: 18 September 2013 07:57
To: dev@cloudstack.apache.org
Subject: [ACS42] Resolved Defects
Please validate and close the following as release is getting closed
1
Shane Witbeck 1
Shanker Balan 1
Sheng Yang 3
shweta agarwal1
Simon Waterhouse 1
Simon Weller 1
Sowmya Krishnan3
Sreekanth Challa 1
Srikanteswararao Talluri2
Sudha Ponnaganti 1
Toshiaki Hatano
This indicates to me that this is tested already
https://issues.apache.org/jira/browse/CLOUDSTACK-4509
-Original Message-
From: Wei ZHOU [mailto:ustcweiz...@gmail.com]
Sent: Wednesday, September 11, 2013 7:37 AM
To: dev@cloudstack.apache.org
Subject: Re: There is no upgrade path from 4.
individual devs to tell us if there's a problem.
I'm still for getting automated test results to be good before calling an RC
vote, as well, to minimize the number of RC re-dos.
On Sep 9, 2013 5:22 PM, "Sudha Ponnaganti"
wrote:
> Would like provide some perspective o
Would like provide some perspective on testing efforts done. All test plans,
results, automation has been posted to community and I took the data from that
only[1].
Thanks for raising the issues around testing before code check-in. This would
help in all fronts esp frontloading quality. Ena
I have posted some baseline metrics [1] on Test case execution, pass rates and
defect incoming rates etc. Pl review. I took data from execution reports that
community has submitted. If I miss any by mistake pl do send report to ML and I
can update and post latest metrics. Appreciate all the hard
Published baseline metrics for automation runs for 4.2. Thanks for all those
who are worked and still continue to fix the failures in test cases. Great
progress and a few more strides to go.
https://cwiki.apache.org/confluence/display/CLOUDSTACK/ACS+4.2+Automation+Results+-+Baseline
Srikanteswararao Talluri2
Sudha Ponnaganti 1
Toshiaki Hatano2
Venkata Siva Vijayendra Bhamidipati 4
venkata swamybabu budumuru 2
XxYton 1
Grand Total250
Thanks
/sudha
Pl close the following defects after validation. If there are any that are not
fixed, pl reopen them
Reporter Total
Abhinandan Prateek 2
Abhinav Roy 2
Ahmad Emneina 2
Alena Prokharchyk 12
angeline shen7
Anthony Xu4
Ashutosk Kelkar
a RC gets built, we are taking a
large quality risk.
On Wed, Aug 28, 2013 at 9:17 AM, Sudha Ponnaganti <
sudha.ponnaga...@citrix.com> wrote:
> For any release - RC validation involves validation of release
> artifacts only but not actual testing. All Test cycles should be
> close
For any release - RC validation involves validation of release artifacts only
but not actual testing. All Test cycles should be closed before we even build
RC itself.
-Original Message-
From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
Sent: Wednesday, August 28, 2013 7:12 AM
AM, "Sudha Ponnaganti"
wrote:
>Even so, expectation is those would also be picked up and closed.
>
>From: Alena Prokharchyk
>Sent: Friday, August 23, 2013 3:08 PM
>To: dev@cloudstack.apache.org; Sudha Ponnaganti
>Subject: Re: [ACS42] Closing resolved issues
>
>Sudha, I
Even so, expectation is those would also be picked up and closed.
From: Alena Prokharchyk
Sent: Friday, August 23, 2013 3:08 PM
To: dev@cloudstack.apache.org; Sudha Ponnaganti
Subject: Re: [ACS42] Closing resolved issues
Sudha, I think we should change the filter to exclude the bugs when the
It was good to have but never a blocker for release from prior releases.
However if community can close critical/blockers atleast that would help
greatly to have confidence in the fixed areas.
-Original Message-
From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
Sent: Friday, A
Hi All,
Community has closed 1477 defects in 4.2. However still another 274 resolved
defects are pending to be closed. Please validate the fix done for the issue
reported by you and close it if you are happy with the fix. If issue is not
fixed, pl reopen it so whoever fixed would get a chance t
Wanted to recheck if anyone is interested to do this. If you have done it
already, pl do share the results with community. There are quite a few users
that are using 4.1/ 4.0, can you try this upgrade path.
Thanks
/sudha
From: Sudha Ponnaganti
Sent: Thursday, August 22, 2013 7:02 AM
To: dev
+1 on JIRA filter
-Original Message-
From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
Sent: Thursday, August 22, 2013 10:23 AM
To: dev@cloudstack.apache.org
Subject: [ACS42] CHANGES file
I am working on preparing for RC and we have a CHANGES file that lists new
features
From: Sudha Ponnaganti
Sent: Thursday, August 22, 2013 7:02 AM
To: us...@cloudstack.apache.org
Subject: [ACS42] Upgrade from 4.0 and 4.1 to 4.2
Hi,
Reaching out to community to see if someone would be interested to upgrade from
ACS 4.0/4.1 to ACS 4.2. If you do, can you share your results
Unless you are fixing a defect for 4.2 please refrain from checking new code in
to 4.2 at this time. RC is supposed to be cut yesterday and will be done in any
minute. Any new code would introduce stability issues.
Appreciate all of your understanding at this time.
Thanks
/Sudha
-Origina
1 - 100 of 210 matches
Mail list logo
