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
: +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 (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,
+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.
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
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
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
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
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
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
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
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
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".
Sudha Ponnaganti would like to recall the message, "VM snapshots".
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
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
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.
___
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
: [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
,
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
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
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
Also open defects need to be addressed as testing has been done on feature
branch and the numbers seem to be high on this branch - atleast blocker and
critical should be addressed.
Key Summary AssigneeReporterPriorityStatus
CLOUDSTACK-2586 [Object_Store_Refactor] Ext
John,
Usually testing of templates require regression testing which usually take ~2
week ( need to run core regression on them ). It is usually preferred to test
templates early on in release given the risk and also it would get enough
coverage by all the testing that happens during release cyc
them in their current state and test
for 4.1? Would additional resources from the community help shorten the
regression test (i.e. is this a nine women make a baby in one month scenario)?
Thanks,
-John
On May 21, 2013, at 10:33 PM, Sudha Ponnaganti
wrote:
> John,
>
> Usually t
Should be fine Swamy,
Test plans are not categorized based on release but test execution results are
so that is how I have setup the structure. You will find test execution
results under each ACS release specific to that release.
Thanks
/sudha
-Original Message-
From: Venkata SwamyBa
I will attend
-Original Message-
From: Joe Brockmeier [mailto:j...@zonker.net]
Sent: Tuesday, May 28, 2013 7:44 AM
To: dev@cloudstack.apache.org
Subject: IRC Meeting Tomorrow? (Wednesday, May 29)
Hey all,
The regular scheduled time for the weekly IRC meeting is 17:00 UTC tomorrow.
We
All the best!
-Original Message-
From: Sebastien Goasguen [mailto:run...@gmail.com]
Sent: Wednesday, May 29, 2013 1:38 AM
To: dev@cloudstack.apache.org
Cc: Dharmesh Kakadia; Meng Han; Ian Duffy; Nguyen Anh Tu; Shiva Teja
Subject: [GSOC] Community Bonding Period
Hi Dharmesh, Meng, Ian, Ng
4.2 already has lot of features ( Around 70+ features ) added and require
hardening once feature freeze happens. This release is bigger than any other
release. Even though 1 round of testing is being done for majority of the
features, there are quite a few that require community help to build q
Hi All,
While voting is in progress for 4.1, can you take a look at the following
features which are still in open/resolved state.
If a story is in resolved state, can reporter review it and close it??
If a story is in open state( there are 4 in the below list) I would think it
will be moved to
+1 on limiting feature proposals for 1 week so scope would not increase
dramatically.
+1 on the time line proposed - The extension proposed by Animesh would help to
close feature which are almost ready for check-in but need quality checks. This
would help for overall quality.
-Original
+1 [binding]
Given that there are around 47 features that are still in Open state,
community can focus on cleaning up that part before feature freeze date. As
indicated in Chip's original mail and indicated in Animesh' s mail below, I
assume that no new proposals will be accepted in to 4.2. S
Hi All,
The following features are done and merged in to Master but need community
contribution to pick these up for validation. There are around 46 features
completed so far and out of which the following 5 do not have QA tasks picked
up.
Calling on community to pick these up for validation
Hi All,
Following features are done by development and marked as resolved. Each of
these stories have QA/Docs/Automation sub-tasks. Calling on community to take
action on marking sub tasks as completed if done already, so these can be
closed. Also some may need coverage esp docs and automation.
Hi,
I have posted Supported Vs Tested Compatibility matrix for ACS 4.2 [1]. Pl do
review and provide feedback.
Areas that you can focus
- Base versions for Upgrades
- Xen versions
- OVM support - I would remove this but just kept it for review for
time being
-
+1 Feature freeze and even RC timelines should not be applicable to automation
tests at this time. BVT and other regression tests would continue to be
developed beyond release date as well in reality. So dates should not hold for
Automation.
However having some timeline restriction would hel
Animesh,
Couple of things :
- Thinking to have a Tuesday defect close day to see if there would be any
interest to have folks participate. This is dedicated day to focus on closure
of defects. Once FF is done, community might be working on closing the defects
and till then main focus is to c
Thanks Prasanna for focusing in this area.
-Original Message-
From: Prasanna Santhanam [mailto:t...@apache.org]
Sent: Sunday, June 09, 2013 7:34 PM
To: CloudStack Dev
Cc: Girish Shilamkar; Rayees Namathponnan; Srikanteswararao Talluri; Shane
Witbeck; Sudha Ponnaganti
Subject
Hi Wido,
This is regarding Ceph integration validation related to the following tickets
https://issues.apache.org/jira/browse/CLOUDSTACK-574
https://issues.apache.org/jira/browse/CLOUDSTACK-1191
If someone want to validate Ceph integration with Cloudstack, what are the
requirements and also is
aster branch, add Ceph primary
storage and see if it works.
A second pair of eyes on the code is always welcome, since I probably forgot
something.
Wido
On 06/12/2013 03:36 AM, Sudha Ponnaganti wrote:
> Hi Wido,
>
> This is regarding Ceph integration validation related to the follow
Ok - thanks for clarification!
-Original Message-
From: Wido den Hollander [mailto:w...@widodh.nl]
Sent: Tuesday, June 11, 2013 11:20 PM
To: dev@cloudstack.apache.org
Subject: Re: [ACS42] Ceph Storage Integration with Cloudstack -
On 06/12/2013 07:38 AM, Sudha Ponnaganti wrote
Also another area to consider is to fix automation test case failures /
automating test cases as it is heavy python based framework.
-Original Message-
From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
Sent: Wednesday, June 12, 2013 12:11 PM
To: dev@cloudstack.apache.org
Subjec
Thanks John for summary. From QA stand point it would make sense to merge once
- assigned test cases are executed and pass rate is on par with release
criteria ( test plans published and execution results are being posted)
- automation runs are successful and shows same pass rate as Master
- blo
storage refactor Meeting Notes
Sudha,
The current plan is to merge once. We explored the feasibility of decomposing
it into independent, testable chunks, and determined it was not possible.
Thanks,
-John
On Jun 13, 2013, at 12:54 PM, Sudha Ponnaganti
wrote:
> Thanks John for summary. F
Daily automated email with BVT test results would be helpful.
-Original Message-
From: Prasanna Santhanam [mailto:t...@apache.org]
Sent: Friday, June 14, 2013 10:43 PM
To: dev@cloudstack.apache.org
Subject: Infra Issues from the IRC meeting (Wed, Jun 12)
Saw a few infra topics being dis
Thanks Prasanna,
This would help to check daily if we are making progress or not on getting the
failed TC fixed.
Requesting community to see the failed TCs and help to fix product issues.
Automation tag has been used for defects logged for the failures.
As suggested in IRC Meeting, we can sto
Hi,
Animesh mentioned that he is offline this week, so I am sending the report
Current status of new features and Improvements [1].
-Some cleanup is required as there are 54 tickets in resolved status. Once Dev
/ QA and Doc activity is done, we can close these. If those respective owners
can t
Below is summary of defect status [1]
- Unassigned and unresolved should be picked up by community members.
Pl review if you can take them up (atleast blockers and critical on priority)
Un Assigned and Un resolved
Blocker 8
Critical 21
Major
Ideally I would like to see all validation to be done on feature branch - BVTs
and also manual validation of the P1 test cases from VM Sync test plan just
like object store validation - sadhu has signed up for it along with Ilya. This
would help us to identify feature specific issues.
We are r
Hi,
Following 2 issues are blocking automation runs - can these be fixed ASAP. If
check-ins are not done to fix these in 24 hours, we have to revert the changes
that caused these failures.
CLOUDSTACK-3167 [Automation] List VLAN range API call failed with null
pointer exception
List of blockers - pl take ownership of unassigned ones. Need to address these
aggressively. QA would be blocked on validation or automation if these are not
addressed.
KeySummary Assignee
CLOUDSTACK-643KVM snapshots deleted on UI/API do not physically
delete fr
Pl do revert if it doesn't cause other issues.
-Original Message-
From: Prachi Damle [mailto:prachi.da...@citrix.com]
Sent: Friday, June 28, 2013 1:44 PM
To: dev@cloudstack.apache.org
Subject: RE: On master updatephysicalnetwork won't enable the phy. net?
Yes seeing this issue too.
Che
Hi All,
Calling on community to see if someone is interested to pick up this plugin for
validation
Require the following to close validation aspect for this plug-in:
- Functional test plan/ Automated tests to test this plug-in
- see cwiki for test plan template[1] and test results templates[2]
-Original Message-
From: Sudha Ponnaganti [mailto:sudha.ponnaga...@citrix.com]
Sent: Saturday, June 29, 2013 4:00 AM
To: dev@cloudstack.apache.org
Subject: RE: [ACS42] Feature Freeze reminder
Hi All,
Calling on community to see if someone is interested to pick up this plugin for
validation
Just want to confirm if upgrades are all enabled for 4.2??
-Original Message-
From: Trippie [mailto:trip...@gmail.com] On Behalf Of Hugo Trippaers
Sent: Saturday, June 29, 2013 10:31 AM
To: dev@cloudstack.apache.org
Subject: Re: [ACS42] Branch created
Great!
I've setup the basic build j
+1 to use code name during dev cycles and name the version for GA release for
reasons outlined by John B. When querying metrics also would help to identify
which defects are logged pre release and which came in post release i.e GA.
-Original Message-
From: John Burwell [mailto:jburw...@
,
-John
On Jul 2, 2013, at 9:24 AM, Sudha Ponnaganti
wrote:
> +1 to use code name during dev cycles and name the version for GA release for
> reasons outlined by John B. When querying metrics also would help to identify
> which defects are logged pre release and which came in post relea
On Jul 2, 2013, at 9:47 AM, Sudha Ponnaganti
wrote:
> Yes - it can be changed in JIRA unless some workflow is set up not to do that
> in ACS.
> However I think we can leave the defects logged before release with codename.
> I do not see a reason that they should be
Can someone shed some light on this missing feature??
-Original Message-
From: Prasanna Santhanam [mailto:t...@apache.org]
Sent: Wednesday, July 03, 2013 7:13 AM
To: dev@cloudstack.apache.org
Cc: Mice Xia; Marcus Sorensen; hongtu_z...@tcloudcomputing.com
Subject: Re: disk resize support o
+1 - let us not remove them. If they are not suitable for BVT, include them in
regression suite.
-Original Message-
From: Ahmad Emneina [mailto:aemne...@gmail.com]
Sent: Thursday, July 04, 2013 3:09 AM
To: dev@cloudstack.apache.org
Subject: Re: Verifying Load Balancer logic
why would w
Swift was tested for older version of Citrix release. There were no code
changes or certification requests, so that area was deprioritized.
Thanks
/Sudha
-Original Message-
From: Edison Su [mailto:edison...@citrix.com]
Sent: Monday, July 08, 2013 10:15 AM
To: 'Chip Childers';
Subject:
All,
There are 543 defects in Resolved state and not closed. Please make sure that
you validate and close the defect if you are satisfied with the fix. If there
are issues with the fix, pl reopen the defect. Pl note that these need to be
validated in 4.2 branch as all are fixed in 4.2 ( should
It was tested pre-4.0 release. As mentioned earlier, there were no changes or
reported issues in this area.
-Original Message-
From: Animesh Chaturvedi
Sent: Monday, July 08, 2013 3:11 PM
To: dev@cloudstack.apache.org; 'Chip Childers'; Sudha Ponnaganti
Subject: RE: Swift
supported in 4.2?
> -Original Message-
> From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
> Sent: Monday, July 08, 2013 3:11 PM
> To: dev@cloudstack.apache.org; 'Chip Childers'; Sudha Ponnaganti
> Subject: RE: Swift in 4.2 is broken, anybody wants
.
[1] https://cwiki.apache.org/confluence/display/CLOUDSTACK/Test+Plans
-Original Message-
From: Angeline Shen
Sent: Monday, July 08, 2013 4:05 PM
To: Sudha Ponnaganti; 'dev@cloudstack.apache.org'; Animesh Chaturvedi;
'chip.child...@sungard.com'
Cc: Sangeeth
Hi,
Wanted to check if there is any TCM instance running for Apache. I would like
to request a project for CS in there is there is one already managed.
Thanks
/sudha
ers. Does that make sense?
Thanks,
-John
On Jul 2, 2013, at 11:16 AM, Sudha Ponnaganti
wrote:
> I definitely understand the easy aspect to carry over defects to version
> number for committers and contributors. But we should triage them and move
> them to future or next release a
Citrix QA would test the upgrades on the suggested paths.
> The proposed upgrade paths are CCP3.0.4, CCP3.0.5, CCP3.06, CCP3.0.7 to ACS4.2
So far it is always testing from all versions to current release. Hope with
the suggestion from Hugo/Chip, this can be reduced to checkpoint releases.
Hi,
We are at a stage that BVTs are passing at high %age and below are the test
results. I have posted results early on but we were at a very low %ages and did
not post it even though we are running them on weekly basis on 4.2 code base.
But here are the results as these are a little easy to co
This week BVT runs for Xen also showed higher pass rates > 95%. As community is
fixing issues, hope we can reach 100% soon.
Package FailedPassed SkippedTotal
1 0 0
1
:setup
integration.smoke.test_affinity_gr
We are lagging behind on pass rates compared to Xen and KVM BVTs. Below are the
defects which cause majority of the failures
https://issues.apache.org/jira/browse/CLOUDSTACK-3568
https://issues.apache.org/jira/browse/CLOUDSTACK-3168
https://issues.apache.org/jira/browse/CLOUDSTACK-3792
https://iss
Hi,
Below are the resolved defects that need to be verified and closed. I have
included reporter name so they can verify the issue they have reported. As we
are getting closer to the release, pl confirm that fix is working fine for the
issue you have reported.
Reporter Total
Abh
Community,
Following are the critical and blocker defects that got fixed in 4.2. Pl make
sure to review the fix / validate and close them
Reporter Total
Grand Total309
Prasanna Santhanam 28
Sanjeev N 24
Srikanteswararao Talluri24
Sangeetha Harih
Any changes to system VM templates require considerable testing. Pl do not make
changes at this time for System VM templates unless there is a defect fix
needed.
-Original Message-
From: Rajesh Battala [mailto:rajesh.batt...@citrix.com]
Sent: Wednesday, July 31, 2013 4:35 AM
To: dev@cl
Below defects are resolved for 4.2 - can you pl review, validate and close the
defects. If the fix is not done as per the defect logged, pl reopen the defect
so developer who fixed would get a chance to review the fix before product goes
to GA.
Reporter Total
Grand Total51
Hi All,
Below are total and Blocker/Critical defects in resolved state. Pl take some
time to close them. Even if you get to close Cortical/Blocker that would be
great.
Reporter Total Blocker/Critical
Abhinandan Prateek 1 1
Abhinav Roy 8 7
A
Hi All,
There are still 200+ critical and blocker defects pending to be validated. Even
if a small %age of these gets rejected, that would cause quality issues for
release. Pl make sure to close these ASAP. First column shows Total defects and
second column shows Blocker/Critical. You can prior
Alena/Murali,
Can one of you review and cleanup Hyper-V specific entries??
Thanks
/sudha
-Original Message-
From: Donal Lafferty
Sent: Sunday, August 11, 2013 3:40 PM
To: Animesh Chaturvedi; dev@cloudstack.apache.org; Chip Childers
Cc: Sudha Ponnaganti; Murali Reddy
Subject: RE
Sadhu,
If you don't mind, can you share the test plan with community
Thanks
/sudha
From: Suresh Sadhu [mailto:suresh.sa...@citrix.com]
Sent: Tuesday, August 13, 2013 12:17 PM
To: dev@cloudstack.apache.org
Cc: cloudstack-...@incubator.apache.org
Subject: regarding issues related ceph integration
Hi All,
Following QA Tasks are not closed and require your attention. Can you review
the list and see if these can be resolved/closed.
- For some of these parent story might have been pushed to next
release, in such case set fixed version as "Future"
Thanks
/Sudha
CLOUDSTACK-903
Feature owners / Community members - can you review the following QA subtasks
and see if you can provide some validation report so these can be closed.
Even if you are not developer of the features, you may have used it so pl
provide such type of validation report as well if you happen to have on
Community members,
Pl review fixes done for the issues that you have reported. RC drop date is
getting close and feature developer may not get a chance to fix it if these are
not fixed as per your requirements.
Pl take some time, validate and close
Thanks
/Sudha
project = CLOUDSTACK AND issuet
RE: [ACS42] QA Subtasks that need to be resolved
Sudha:
CLOUDSTACK-903CLOUDSTACK-40 QA - New Image based provisioning
method for Baremetal
IS this new baremetal feature or referring to existing baremetal project?
How to update these 2 bugs ?
Thanks
-Original Message--
Mike,
I have similar concern as well.
We have regression and BVT tests running daily on 4.2 branch locally besides
manual validation of the defects and impacted areas. Even though we would not
be able to catch all the issues, several regressions were caught and you can
see the defects by usi
Hi All,
Pl review and validate the following resolved issues.
Reporter Total
Abhinandan Prateek 2
Abhinav Roy 6
Ahmad Emneina 3
Alena Prokharchyk 20
angeline shen3
Anthony Xu4
Bharat Kumar10
Brian Angus1
Brian Spindler1
C
Last blocker was https://issues.apache.org/jira/browse/CLOUDSTACK-4403 and got
resolved this morning
Can you pl log a defect for this one?
-Original Message-
From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
Sent: Monday, August 19, 2013 1:27 PM
To: dev@cloudstack.apache.org
Su
CLOUDSTACK-921 QA - Ntier Apps 2.0 use same public IP
for static NAT, PF and LB in VPCUnassigned
CLOUDSTACK-2415 CLOUDSTACK-2163 QA Automation : Add ability in CS for
admin to have better control over first class objects Unassigned
Thanks
/sudha
From: Sudha
Thanks all who have worked on these features. All but 2 are closed and
following up on the 2 that are left over.
Thanks
/sudha
From: Sudha Ponnaganti
Sent: Wednesday, August 14, 2013 12:56 PM
To: dev@cloudstack.apache.org
Subject: [ACS42] QA Subtasks that need to be resolved
Hi All,
Following
available
for VPN Customer Gateway Unassigned
Thanks
/sudha
From: Sudha Ponnaganti
Sent: Monday, August 19, 2013 4:08 PM
To: dev@cloudstack.apache.org
Subject: [ACS42] QA Tasks that are not complete
Feature owners/Community members,
Can you pl review these tasks and update them. If anyone
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
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
+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
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
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
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
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
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
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
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
1 - 100 of 210 matches
Mail list logo
