Summary of IRC meeting in #cloudstack-meeting, Wed May 29 17:08:53 2013
Members present: animesh, vogxn, digitalsanctum, talluri, topcloud, sudhap, jzb Meeting summary: 1. Preface 2. active feature release a. sudhap will send reminder to ML to update Jira tickets (jzb, 2) b. animesh will remind developers on ML to move specs to 4.2 for open items from 4.1. (jzb, 2) 3. Master branch a. vogxn to bring up topic of automated tests flow in post freeze (vogxn, 3) 4. Infra a. vogxn to work on automating reports for test runs from the test infra (vogxn, 4) b. sudhap post compatibility matrix: Which upgrades + installs need to be tested for 4.2 (jzb, 4) Actions: - sudhap will send reminder to ML to update Jira tickets (jzb, 17:15:41) - animesh will remind developers on ML to move specs to 4.2 for open items from 4.1. (jzb, 17:17:29) - vogxn to bring up topic of automated tests flow in post freeze (vogxn, 17:24:46) - vogxn to work on automating reports for test runs from the test infra (vogxn, 17:38:54) - sudhap post compatibility matrix: Which upgrades + installs need to be tested for 4.2 (jzb, 17:41:43) IRC log follows: # 1. Preface # 17:08:54 [jzb]: ASFBot: meeting start # 2. active feature release # 17:09:44 [jzb]: Since we're in mid-VOTE for 4.1.0, let's just go through this as one big topic 17:09:52 [jzb]: anything to discuss or report on 4.1.0, anyone? 17:10:43 [animesh]: Assuming the VOTE closes I will move over remaining defects to 4.2 17:10:51 [animesh]: by Friday 17:11:07 [jzb]: OK 17:11:21 [jzb]: I guess that's all for 4.1.0, so let's move on. 17:11:44 [jzb]: Since 4.0.x will be obsoleted by 4.1.0, I'm going to skip active bugfix release unless anyone has something on that. 17:12:04 [sudhap]: one more issue 17:12:13 [jzb]: sudhap: OK 17:12:36 [sudhap]: There are a few more new and improvement stories that need to be closed for 4.1 17:12:51 [sudhap]: if folks can take time to review and close those, it would be clean 17:13:06 [jzb]: sudhap: closed? 17:13:08 [sudhap]: if anything need to be moved to 4.2 we can do 17:13:21 [jzb]: you mean Jira tickets that are still not updated, or...? 17:13:37 [sudhap]: Yes 17:14:05 [sudhap]: JIRA New and Improvements which are not addressed for 4.1 - they may have been but status shows not resolved 17:14:19 [jzb]: sudhap: ah, OK. Have you raised that on the ML? 17:14:27 [animesh]: Sudha can you send a reminder to dev list 17:14:34 [jzb]: we'll want to get those resolved and make animesh's life easier. 17:14:41 [vogxn]: many Major items will be unresolved. are these those ones? 17:15:03 [sudhap]: jzb, animesh: yes 17:15:04 [sudhap]: will send reminder 17:15:26 [vogxn]: sudhap: release exist critieria was Blocker and Critical only. so others would carry over to 4.2 17:15:26 [sudhap]: vogxn: no - these are features but not defects 17:15:33 [vogxn]: sudhap: ah. got it 17:15:41 [topcloud]: someone should go through and remind devs to move their specs to 4.2 as well. 17:15:41 [topcloud]: if it's not in 4.1 17:15:41 [jzb]: #action sudhap will send reminder to ML to update Jira tickets 17:16:11 [topcloud]: same thing with test plans assuming test plans are listed by release as well. 17:16:28 [animesh]: I will take the action item to remind dev on moving specs to 4.2 for open items from 4.1 17:17:06 [topcloud]: animesh: thanks. 17:17:13 [sudhap]: +topcloud: test plans are not listed by release but test execution results are 17:17:28 [topcloud]: sudhap: cool. 17:17:29 [jzb]: #action animesh will remind developers on ML to move specs to 4.2 for open items from 4.1. 17:18:28 [jzb]: anything else on 4.1.0? 17:20:13 [jzb]: I'll take that as a no. 17:20:13 [jzb]: Moving on... # 3. Master branch # 17:21:17 [animesh]: Feature freeze is on friday and we have many open and in progress items 17:21:17 [jzb]: any topics on the master branch, also known as soon-to-be 4.2 branch? 17:21:31 [animesh]: I will send a reminder today 17:21:32 [jzb]: OK 17:22:16 [vogxn]: animesh: automated tests like docs will keep flowing in. is there aany criteria? should i bring up the topic on list? 17:22:23 [sudhap]: animesh: I thinkg status is not updated for some eventhough they are complete - I also need to go through resolved ones and mark them closed if testing and docs are completed for those stories 17:23:01 [animesh]: vogxn: sure go ahead 17:23:31 [animesh]: sudhap: yes you had sent a reminder last week, I will send similar reminder today 17:23:53 [sudhap]: animesh:sure 17:24:10 [jzb]: sudhap: I get confused when you talk about stories instead of tickets ;-) 17:24:31 [vogxn]: +1, stories, tales :) hope our features are real features and not just tall tales :) 17:24:38 [jzb]: heh 17:24:46 [vogxn]: #action vogxn to bring up topic of automated tests flow in post freeze 17:25:16 [sudhap]: jzb:sorry about that 17:25:31 [animesh]: sudha comes from many years on agile teams 17:25:53 [jzb]: gotcha. 17:26:01 [jzb]: other items on Master? 17:26:16 [talluri]: vogxn: what is about "
Summary of IRC meeting in #cloudstack-meeting, Wed Jun 5 17:07:13 2013
Members present: digitalsanctum, kdamage, sebgoa, ke4qqq, sudhap, animeshc, Humbedooh, jzb Meeting summary: 1. Preface 2. Active Feature Release: Overall Status 3. Active Feature Release: Feature Status 4. Active Feature Release: Docs Status a. jzb open discussion on breaking docs out into their own repo (jzb, 4) 5. Active Feature Release: Additional Issues? 6. Active Bug-Fix Release: Overall Status 7. Master branch 8. Infra 9. Others? Actions: - jzb open discussion on breaking docs out into their own repo (jzb, 17:20:44) IRC log follows: # 1. Preface # 17:07:14 [jzb]: ASFBot: meeting start 17:07:24 [jzb]: ASFBot: start meeting 17:07:24 [jzb]: Humbedooh: am I doing it wrong, or is something amiss? 17:08:08 [sudhap]: sudha is here 17:08:13 [jzb]: OK, let's get started # 2. Active Feature Release: Overall Status # 17:08:29 [kdamage]: haha I am indeed here today 17:08:31 [jzb]: do we have any reports, comments, etc. on the overall status. 17:08:36 [jzb]: ? 17:08:43 [Humbedooh]: jzb: freenode DDoS stuff :( 17:08:51 [jzb]: Humbedooh: gotcha 17:09:29 [jzb]: The good news is the active feature release is now 4.2.0, so +1 to that 17:09:46 [ke4qqq]: 4.1 is seeing a few bug reports that are concerning 17:09:53 [ke4qqq]: particularly the ubuntu libvirt problem 17:10:01 [jzb]: ke4qqq: shouldn't we hold that to active bug-fix ? 17:10:28 [ke4qqq]: doh - sorry didn't see topic 17:10:36 [jzb]: ke4qqq: no worries # 3. Active Feature Release: Feature Status # 17:10:58 [jzb]: any reports, comments, discussion on the feature status for 4.2? 17:11:22 [sudhap]: jzb: I went over the features to see which ones do not have QA coverage 17:11:42 [sudhap]: identified 5 stories ( Jira tickets) 17:11:50 [sudhap]: Requested community for coverage - 1 of them has been picked up 17:12:06 [sudhap]: Went over the resolved ones to see progress from QA 17:12:19 [sudhap]: Majority are progressing nicely but status need to be updated 17:12:34 [sudhap]: both for open and resolved stories ( Jira tickets) 17:13:18 [sudhap]: Incoming defect rate has been high as expected 17:13:41 [sudhap]: dashboard shows the status for incoming 17:13:56 [jzb]: sudhap: anything particularly concerning, or situation normal? 17:14:05 [sudhap]: Automation pass rates are very poor 17:14:12 [sudhap]: this is a big concern at this point 17:14:26 [sudhap]: blockers that are causing failure should be prioritized and fixed 17:15:11 [sudhap]: There are 19 blockers and 50+ criticals which causes this pass rate hovering around 70% or so 17:15:58 [sudhap]: Regression pass rates are even worse 17:16:12 [sudhap]: Trying to focus in these are as to get the pass rates up 17:16:24 [sudhap]: Concern is around automation for time being 17:17:03 [sudhap]: specifically around high failure rates - need to bring it up 17:17:05 [sudhap]: I am done 17:17:34 [jzb]: sudhap: thanks! 17:17:41 [jzb]: anybody else? 17:17:56 [jzb]: I think that also catches us up on QA status # 4. Active Feature Release: Docs Status # 17:18:38 [jzb]: I'm going to start release notes this week for 4.2.0 so it's not quite the task next time. 17:19:13 [ke4qqq]: We talked about breaking out docs during 4.0 and 4.1 dev cycle 17:19:21 [ke4qqq]: is that something we want to do now that 4.1 has released 17:19:21 [ke4qqq]: ? 17:19:29 [jzb]: and this time I'm planning on only worrying about upgrade from 4.1.x to 4.2.0 as we are asking people to upgrade to 4.1.0 then later from much earlier versions. 17:20:13 [jzb]: ke4qqq: we could, especially since we've moved the release back 4 weeks 17:20:39 [ke4qqq]: might be time to resurrect that thread on the list 17:20:44 [jzb]: #action jzb open discussion on breaking docs out into their own repo 17:20:58 [sudhap]: jzb - we can prioritize 4.1x -> 4.2 but need to test rest of the upgrade scenarios 17:21:14 [jzb]: sudhap: test is fine, but I'm talking about what we try to document 17:21:24 [sudhap]: oh ok 17:21:43 [sudhap]: would there be explicit documentation that we are going to drop support for any of the older versions?? 17:21:58 [sebgoa]: I am not sure what the implication of having "separate repos" is/are 17:23:13 [jzb]: sudhap: if we do that, yes. 17:23:58 [jzb]: sebgoa: has implications for testing, for one thing. Less to download. 17:24:21 [jzb]: sebgoa: we might want to restructure the guides, too. 17:24:31 [jzb]: but that's probably best discussed on the ML 17:24:46 [sebgoa]: k # 5. Active Feature Release: Additional Issues? # 17:25:36 [jzb]: any additional issues for 4.2.0 we need to raise before talking about bugfix release? 17:25:55 [animeshc]: yes there are large number of resolved issues that yet needs to be closed 17:26:39 [jzb]: animeshc: I think Sudha raised that earlier 17:27:01 [animeshc]: she raised open issues not resolved 17:27:08 [jzb]: ah, OK 17:27:24 [jzb]: animeshc: do we have a report? 17:27:48 [animeshc]: I will send it out today with my reminder, the 4
Summary of IRC meeting in #cloudstack-meeting, Wed Jun 5 17:07:13 2013
Members present: digitalsanctum, kdamage, sebgoa, ke4qqq, sudhap, animeshc, Humbedooh, jzb Meeting summary: 1. Preface 2. Active Feature Release: Overall Status 3. Active Feature Release: Feature Status 4. Active Feature Release: Docs Status a. jzb open discussion on breaking docs out into their own repo (jzb, 4) 5. Active Feature Release: Additional Issues? 6. Active Bug-Fix Release: Overall Status 7. Master branch 8. Infra 9. Others? Actions: - jzb open discussion on breaking docs out into their own repo (jzb, 17:20:44) IRC log follows: # 1. Preface # 17:07:14 [jzb]: ASFBot: meeting start 17:07:24 [jzb]: ASFBot: start meeting 17:07:24 [jzb]: Humbedooh: am I doing it wrong, or is something amiss? 17:08:08 [sudhap]: sudha is here 17:08:13 [jzb]: OK, let's get started # 2. Active Feature Release: Overall Status # 17:08:29 [kdamage]: haha I am indeed here today 17:08:31 [jzb]: do we have any reports, comments, etc. on the overall status. 17:08:36 [jzb]: ? 17:08:43 [Humbedooh]: jzb: freenode DDoS stuff :( 17:08:51 [jzb]: Humbedooh: gotcha 17:09:29 [jzb]: The good news is the active feature release is now 4.2.0, so +1 to that 17:09:46 [ke4qqq]: 4.1 is seeing a few bug reports that are concerning 17:09:53 [ke4qqq]: particularly the ubuntu libvirt problem 17:10:01 [jzb]: ke4qqq: shouldn't we hold that to active bug-fix ? 17:10:28 [ke4qqq]: doh - sorry didn't see topic 17:10:36 [jzb]: ke4qqq: no worries # 3. Active Feature Release: Feature Status # 17:10:58 [jzb]: any reports, comments, discussion on the feature status for 4.2? 17:11:22 [sudhap]: jzb: I went over the features to see which ones do not have QA coverage 17:11:42 [sudhap]: identified 5 stories ( Jira tickets) 17:11:50 [sudhap]: Requested community for coverage - 1 of them has been picked up 17:12:06 [sudhap]: Went over the resolved ones to see progress from QA 17:12:19 [sudhap]: Majority are progressing nicely but status need to be updated 17:12:34 [sudhap]: both for open and resolved stories ( Jira tickets) 17:13:18 [sudhap]: Incoming defect rate has been high as expected 17:13:41 [sudhap]: dashboard shows the status for incoming 17:13:56 [jzb]: sudhap: anything particularly concerning, or situation normal? 17:14:05 [sudhap]: Automation pass rates are very poor 17:14:12 [sudhap]: this is a big concern at this point 17:14:26 [sudhap]: blockers that are causing failure should be prioritized and fixed 17:15:11 [sudhap]: There are 19 blockers and 50+ criticals which causes this pass rate hovering around 70% or so 17:15:58 [sudhap]: Regression pass rates are even worse 17:16:12 [sudhap]: Trying to focus in these are as to get the pass rates up 17:16:24 [sudhap]: Concern is around automation for time being 17:17:03 [sudhap]: specifically around high failure rates - need to bring it up 17:17:05 [sudhap]: I am done 17:17:34 [jzb]: sudhap: thanks! 17:17:41 [jzb]: anybody else? 17:17:56 [jzb]: I think that also catches us up on QA status # 4. Active Feature Release: Docs Status # 17:18:38 [jzb]: I'm going to start release notes this week for 4.2.0 so it's not quite the task next time. 17:19:13 [ke4qqq]: We talked about breaking out docs during 4.0 and 4.1 dev cycle 17:19:21 [ke4qqq]: is that something we want to do now that 4.1 has released 17:19:21 [ke4qqq]: ? 17:19:29 [jzb]: and this time I'm planning on only worrying about upgrade from 4.1.x to 4.2.0 as we are asking people to upgrade to 4.1.0 then later from much earlier versions. 17:20:13 [jzb]: ke4qqq: we could, especially since we've moved the release back 4 weeks 17:20:39 [ke4qqq]: might be time to resurrect that thread on the list 17:20:44 [jzb]: #action jzb open discussion on breaking docs out into their own repo 17:20:58 [sudhap]: jzb - we can prioritize 4.1x -> 4.2 but need to test rest of the upgrade scenarios 17:21:14 [jzb]: sudhap: test is fine, but I'm talking about what we try to document 17:21:24 [sudhap]: oh ok 17:21:43 [sudhap]: would there be explicit documentation that we are going to drop support for any of the older versions?? 17:21:58 [sebgoa]: I am not sure what the implication of having "separate repos" is/are 17:23:13 [jzb]: sudhap: if we do that, yes. 17:23:58 [jzb]: sebgoa: has implications for testing, for one thing. Less to download. 17:24:21 [jzb]: sebgoa: we might want to restructure the guides, too. 17:24:31 [jzb]: but that's probably best discussed on the ML 17:24:46 [sebgoa]: k # 5. Active Feature Release: Additional Issues? # 17:25:36 [jzb]: any additional issues for 4.2.0 we need to raise before talking about bugfix release? 17:25:55 [animeshc]: yes there are large number of resolved issues that yet needs to be closed 17:26:39 [jzb]: animeshc: I think Sudha raised that earlier 17:27:01 [animeshc]: she raised open issues not resolved 17:27:08 [jzb]: ah, OK 17:27:24 [jzb]: animeshc: do we have a report? 17:27:48 [animeshc]: I will send it out today with my reminder, the 4
Summary of IRC meeting in #cloudstack-meeting, Wed Jun 12 17:08:56 2013
Members present: Animesh, sudhap, dahn, topcloud, kelveny, chipc, ke4qqq, jzb Meeting summary: 1. Preface 2. Active Feature Release: Overall Status 3. Active Feature Release QA Status 4. Active Feature Release: Doc Status 5. Active Feature Release: Additional Issues 6. Active Bug Fix Release: 4.1.1 7. Master Branch 8. Infra 9. Other topics? IRC log follows: # 1. Preface # # 2. Active Feature Release: Overall Status # 17:09:36 [jzb]: what do we have on the 4.2.0 status? 17:09:43 [dahn]: chipc: thanks, will read it 17:09:56 [kelveny]: we are targeting to merge vmsync branch 17:09:56 [Animesh]: On 4.2 there are many open defects 17:10:04 [Animesh]: kelven go ahead 17:10:25 [kelveny]: code changes is targeted to complete by the end of this week 17:10:42 [kelveny]: after that official merge request will be sent to the list 17:11:06 [kelveny]: actually merge may happen at next week if no objections 17:11:26 [chipc]: kelveny: I'm curious about what testing is happening on that branch 17:11:44 [ke4qqq]: BVT at least? 17:11:51 [kelveny]: we will try to setup BVT test on the branch 17:12:16 [chipc]: that seems like a pre-requisite to merge, when I look at the complexity of the work 17:12:22 [chipc]: so +1 to that! 17:12:41 [kelveny]: most of infrastructure tests are already done through unit tests 17:13:18 [chipc]: sweet! 17:13:38 [kelveny]: but we do have refactoring changes in areas that is not possible for unit test, will rely on BVT for integration test 17:13:43 [chipc]: BTW - that's a really good FS... it made it possible to grok the changes 17:13:58 [chipc]: (or at least most of them) 17:15:13 [kelveny]: that's pretty much the update from my side 17:15:21 [jzb]: thanks kelveny 17:15:28 [jzb]: Animesh: did you have more? 17:15:56 [Animesh]: yes the defect resolution rate has been more than the incoming defects so looks like we are getting better 17:16:39 [Animesh]: but still we have large number of open defects, Sudha will also share test results to help everyone guage our readiness 17:17:37 [dahn]: newbee question about defects, please 17:17:58 [Animesh]: dahn: sure what's the question? 17:18:14 [dahn]: If i use an api in master, and it breaks after an update do I report a defect in jira ? 17:18:22 [dahn]: or talk to someone off line 17:18:27 [dahn]: or the list? 17:18:40 [Animesh]: filing a defect is best 17:18:53 [jzb]: dahn: is it an API that also works in a release? 17:19:11 [jzb]: I wouldn't necessarily say something's a defect if an API changes in master. 17:19:17 [jzb]: that isn't in a release. 17:19:35 [dahn]: jzb: I have to investigate. I think so 17:19:43 [dahn]: Animesh: does that mean jira?\ 17:19:54 [jzb]: dahn: OK. then what Animesh said. :-) 17:19:59 [Animesh]: dahn: yes we use JIRA for defect tracking 17:20:00 [topcloud]: that should be a bug. comparing it to a previous release provides details to a bug. 17:20:21 [topcloud]: we shouldn't treat master different. 17:20:49 [dahn]: thanks, all 17:20:56 [dahn]: you will hear of me 17:22:13 [Animesh]: continuing on the release, I will encourage folks to check on 4.2 Release dashboard 17:22:44 [Animesh]: I will send out my weekly reminder today on status and include Sudha's test results 17:23:28 [topcloud]: one thing that concerns me is that the bvt continues to be at < 100% pass rate 17:23:41 [topcloud]: is there anything we're doing about this? 17:23:47 [Animesh]: After the feature freeze date 6/28 i will send out daily emails since we need focused activity to resolve and close our back log of defects 17:24:44 [Animesh]: topcloud: on bvt issues rayees and other have been filing defects that are triaged daily 17:25:20 [chipc]: topcloud: was BVT ever at 100% ? 17:25:32 [chipc]: (real question, not sarcasm) 17:25:44 [topcloud]: chipc: to my understanding, it was at one point >95% 17:26:17 [sudhap]: Yes - they were 100% before 4.1 but since then we never had 100% 17:26:41 [chipc]: once we get it back to 100%, I say we block all changes when it drops to <100% 17:26:49 [topcloud]: +1 17:26:56 [chipc]: anyway, that was a distraction from the 4.2.0 topic 17:26:59 [chipc]: (sort of) 17:27:25 [jzb]: anything else on 4.2.0 overall status? 17:27:37 [topcloud]: not really...I think bvt not being at 100% is a big part of why 4.1 was delayed. 17:27:42 [topcloud]: don't want to see it happen for 4.2. 17:28:07 [Animesh]: agreed bvt also shows progress towards release readines 17:28:07 [chipc]: topcloud: +1 17:28:32 [chipc]: Animesh: BVT should show that master is stable, regardless of release timeframes 17:28:33 [chipc]: IMO that is 17:28:44 [chipc]: master should only see good /tested code 17:28:56 [chipc]: but I'm repeating myself I think... so back to the corner for me! 17:28:57 [Animesh]: one more thing on my side was we had a GTM on object_store, john burwell took the action item to update the dev-list 17:29:23 [jzb]: OK # 3. Active Feature Release QA Status # 17:29:59 [jzb]: do
Summary of IRC meeting in #cloudstack-meeting, Wed Mar 27 17:05:21 2013
Members present: Animesh, sudhap, vogxn, Chandan, sangeetha, chipc, ke4qqq, jzb Meeting summary: 1. Preface 2. Active Feature Release: Overall Status a. http://markmail.org/message/3sh4ftyedjcmycyn (chipc, 2) b. http://markmail.org/message/ibxqqxddzqbxv4bx (chipc, 2) 3. Active Feature Release: Feature Status 4. Active Feature Release: QA 5. Active Feature Release: Doc Status 6. Active Feature Release: Additional Issues? 7. Active Bug-Fix Release 8. Master Branch 9. Infra 10. Others? a. sudhap to start discussion about developer priorities on ML (jzb, 10) Actions: - sudhap to start discussion about developer priorities on ML (jzb, 17:55:56) IRC log follows: # 1. Preface # 17:05:43 [jzb]: Reminder that the agenda is here: https://cwiki.apache.org/confluence/display/CLOUDSTACK/IRC+Meetings+%28Logs+and+Minutes%29 # 2. Active Feature Release: Overall Status # 17:06:07 [jzb]: anyone want to report on the overall status of 4.1.0? 17:06:13 [chipc]: sure 17:06:36 [chipc]: so, by my count, and in my last email, we have 1 blocker and 6 critical bugs that need to be resolved before I'll cut the RC 17:06:43 [chipc]: #info http://markmail.org/message/3sh4ftyedjcmycyn 17:06:58 [chipc]: the blocker looks like it will probably be an easy fix for Min, but we'll have to wait to hear back 17:07:21 [chipc]: the critical ones, a chunk are assigned to Kelven... who has noted that they are fixed pending merge 17:07:36 [chipc]: I'm just not sure if they were fixed in the big merge I did this morning for him 17:07:58 [chipc]: Mural's bug (1673) has a fix pending, but also requires one of Kelven's bugs to be fixed 17:08:13 [chipc]: and there's one for Kishan (1819) that needs to also be addressed 17:08:28 [chipc]: sudhap also mentioned that we were blocked on upgrade testing 17:08:36 [chipc]: so that's a pre-req as well 17:08:43 [chipc]: and that's that... questions? 17:08:51 [vogxn]: Kishan's away at a conference and will be back hopefully tomorrow. So if it can be taken care of by someone PST great. if not i'll talk to kishan 17:08:58 [ke4qqq]: whats the upgrade problem? 17:09:13 [chipc]: ke4qqq: testing was blocked, something related to the Spring AOP stuff 17:09:23 [chipc]: ACTION goes to find sudhap's email 17:09:43 [Animesh]: I will ask Prachi to look at Kishan's defect 1819 17:09:51 [vogxn]: Animesh: thx 17:09:51 [chipc]: #info http://markmail.org/message/ibxqqxddzqbxv4bx 17:09:58 [chipc]: ke4qqq: ^^ 17:10:07 [chipc]: Animesh: thx 17:10:37 [jzb]: anything else on the 4.1.0 overall status? 17:11:13 [chipc]: not from me 17:11:21 [jzb]: OK, let's move to the next topic 17:11:21 [chipc]: I'd like to get to the place where I can cut the RC obviously 17:11:22 [chipc]: ;-) # 3. Active Feature Release: Feature Status # 17:11:53 [jzb]: do we have anything to report on feature status? 17:12:07 [ke4qqq]: isn't 4.1 the active feature release? 17:12:23 [chipc]: jzb: that agenda item doesn't apply after feature freeze ;-) 17:12:36 [jzb]: fair enough 17:12:43 [jzb]: chipc: though, perhaps bare metal might apply here 17:12:43 [chipc]: however, I guess, just to be compelte... we did pull baremetal 17:12:51 [jzb]: if there were anything needed to discuss 17:12:51 [chipc]: that! 17:12:51 [jzb]: :-) 17:13:07 [chipc]: it's disabled now, and I *hope* the last bugs introduced by disabling it are now resolved 17:13:28 [jzb]: OK, next up... # 4. Active Feature Release: QA # 17:14:21 [jzb]: anyone have anything to report on QA? 17:14:59 [ke4qqq]: vogxn: can you provide an update? 17:15:00 [sangeetha]: Upgrade still has issues .. 17:15:21 [chipc]: sangeetha: ack - and do we have blocker / critical bugs to track? 17:15:22 [sangeetha]: https://issues.apache.org/jira/browse/CLOUDSTACK-1694 - Tracked in this issue 17:16:21 [chipc]: sangeetha: thanks... looks like it was reopened today 17:16:21 [sangeetha]: We have few other critical issues relating to Events and AWS currently 17:16:51 [chipc]: sangeetha: was it in the list of bugs I listed here: http://markmail.org/message/3sh4ftyedjcmycyn 17:17:06 [sangeetha]: Yes ..we still need an upgrade path where we update binaries , start the management server and things work 17:17:06 [chipc]: if so, I think I discussed above 17:17:13 [chipc]: indeed 17:17:24 [Chandan]: I will be testing EC2 Rest API feature after verification of https://issues.apache.org/jira/browse/CLOUDSTACK-1812 17:17:37 [chipc]: hopefully Pradeep can help get through the upgrade process 17:17:58 [sangeetha]: He just assigned this issue to Marcus 17:18:29 [chipc]: ok, hopefully marcus then ;-) 17:18:44 [ke4qqq]: ACTION wishes marcus was on irc 17:18:54 [jzb]: looks like Marcus replied not too long ago + was on it. 17:19:13 [chipc]: ok, so we can't get much more done in this mtg around it 17:19:36 [jzb]: ok, next topic all? 17:19:37 [ke4qqq]: wfm # 5. Active Feature Release: Doc Status # 17:20:36 [jzb]: we're down to 12 bugs for doc
Summary of IRC meeting in #cloudstack-meeting, Wed Apr 3 17:04:15 2013
Members present: sangeetha, jzb, topcloud, vogxn, sudhap, chipc, kdamage, widodh Meeting summary: 1. Preface 2. 4.1 overall status 3. 4.1 QA updates 4. 4.1 docs 5. 4.1 other items 6. master branch a. vogxn to notify the ML about how to test via BVT prior to a push (chipc, 6) 7. other topics Actions: - vogxn to notify the ML about how to test via BVT prior to a push (chipc, 17:36:09) IRC log follows: # 1. Preface # 17:04:44 [chipc]: so we might have a light meeting today, given that the citrix folks are in a $dayjob meeting 17:04:59 [chipc]: but we'll do the usual - start with 4.1, then discuss master and then other topics 17:05:00 [chipc]: so... # 2. 4.1 overall status # 17:05:21 [chipc]: We're close with 4.1 to an RC 17:05:36 [chipc]: as it stands now, we have 1 blocker: CLOUDSTACK-1877 17:05:51 [chipc]: and 4 critical bugs 17:06:08 [chipc]: CLOUDSTACK-1877 17:06:21 [chipc]: widodh: I assigned that one to you, given your comments 17:06:29 [chipc]: are you doing ok with the fix? 17:06:36 [widodh]: chipc: Yes, I'm working on that one 17:06:45 [chipc]: excellent... any ETA? 17:06:53 [widodh]: seems a packaging issues and the mgmt server opens a wrong db.properties 17:07:37 [chipc]: is it the type of bug that will take a day or so? or perhaps today? 17:07:44 [widodh]: chipc: I think I have it "fixed" locally 17:07:51 [kdamage]: goodmorning 17:07:51 [chipc]: excellent - so you're just testing the fix before pushing 17:07:59 [chipc]: good deal 17:07:59 [widodh]: I'm not sure, it seems like a encryption issue. Not sure what it is yet 17:08:06 [chipc]: hm 17:08:06 [widodh]: chipc: I just disabled encryption and everything works 17:08:16 [widodh]: chipc: It also fixed my agent issues, with them not connecting 17:08:29 [chipc]: alrighty then... I guess shout on the ML if you need help 17:08:44 [chipc]: oh good, I was going to ask about the agent connection issue too 17:08:46 [chipc]: ok, next one 17:08:47 [chipc]: CLOUDSTACK-1837 17:08:52 [widodh]: chipc: Was planning on doing so. 17:09:06 [chipc]: jzb has that one, and it's really just the upgrade procedure 17:09:16 [chipc]: jzb: will perhaps ask you about docs generally in that topic 17:09:29 [chipc]: CLOUDSTACK-1842 17:09:51 [widodh]: chipc: Asking me about it? 17:09:59 [chipc]: widodh: no 17:10:14 [chipc]: 1842 is assigned to Abhi, but I haven't seen any updated in the ticket or to my ML questions about it 17:10:26 [chipc]: so we're still waiting to hear about 1842 17:10:46 [chipc]: CLOUDSTACK-1868 17:11:09 [chipc]: Sateesh has that one assigned, and again no updates on it 17:11:18 [chipc]: hopefully it can be looked at in the next day 17:11:31 [chipc]: last one: 17:11:31 [chipc]: CLOUDSTACK-1874 17:11:46 [chipc]: 1874 may not be a critical bug, given the comments 17:12:09 [chipc]: but I'm waiting to hear back from Kishan on if there is a fix or not that's easily applied 17:12:18 [chipc]: and that's it for the bug list... 17:12:31 [widodh]: chipc: About 1842, that's just a DB thingie 17:12:46 [widodh]: I've looked at it some months ago, but wasn't that special 17:12:48 [chipc]: widodh: check the ML for a thread where I asked about it 17:12:54 [chipc]: perhaps we can resolve easily 17:13:24 [chipc]: I'd be willing to make the fix, but I was looking for a response that it was the right way to do it 17:13:24 [topcloud]: chipc: I believe it can be resolved quickly. region no longer keeps track of where an account is created. 17:13:39 [chipc]: topcloud: you mean 1874? 17:13:54 [chipc]: topcloud: I agree - I just need a patch to fix it 17:13:54 [topcloud]: yes...that's the current topic? 17:14:16 [chipc]: topcloud: we were jumping around a little 17:14:24 [widodh]: chipc: I'll check the ml regarding that. It's just that 1877 already took me a whole day today. 17:14:39 [chipc]: widodh: understood 17:14:46 [topcloud]: chipc: i'll take it up 1847. 17:14:49 [topcloud]: 1874 17:14:54 [chipc]: topcloud is 1874 as easy as just removing that column from the SQL? 17:15:01 [chipc]: topcloud: excellent... thank you 17:15:03 [chipc]: assinging to you now 17:15:24 [chipc]: ok, moving on # 3. 4.1 QA updates # 17:15:46 [chipc]: does anyone want to provide a 4.1 QA overview today? 17:16:01 [sudhap]: chipc: Upgrade testing is one that is being tested 17:16:01 [chipc]: I know I just went through the bugs, but is there still testing outstanding? 17:16:09 [sangeetha]: I had started a tread on component.xml and db.properties for upgrade 17:16:09 [chipc]: sudhap: cool 17:16:19 [chipc]: sangeetha: ack - we need people to reply 17:16:39 [chipc]: topcloud / widodh: mind looking at sangeetha's thread? 17:16:46 [widodh]: chipc: sangeetha: db.properties is already fixed in both RPM and DEB 17:17:09 [widodh]: they copy the old one to the new location. components.xml is a lot harder, no way to merge that script-wise 17:17:19 [topcloud]: chipc: i did take a quick look. it's a tough problem. 17:17:40 [
Summary of IRC meeting in #cloudstack-meeting, Wed Apr 10 17:05:03 2013
Members present: Animesh, vogxn, chipc, Humbedooh, jzb, sangeetha, ke4qqq, kdamage_, edison_cs, sudhap_, Chandan, serverchief, sudhap Meeting summary: 1. Preface 2. Active Feature Release: Overall Status 3. Active Feature Release: QA Status 4. Active Feature Release: Docs Status a. sangeetha file a jira doc bug for the IPv6 template procedure (jzb, 4) 5. Active Feature Release: Additional Issues? 6. Active Bugfix Release 7. Master Branch a. Animesh put out tentative schedule for 4.2.0 (jzb, 7) 8. Infra 9. Others? Actions: - sangeetha file a jira doc bug for the IPv6 template procedure (jzb, 17:24:31) - Animesh put out tentative schedule for 4.2.0 (jzb, 17:31:09) IRC log follows: # 1. Preface # 17:05:31 [jzb]: reminder - it's courteous to end your comments, etc. with EOF when you're done talking so we know you're done # 2. Active Feature Release: Overall Status # 17:05:54 [jzb]: chipc: want to take it away? 17:05:56 [chipc]: overall status = we have some bugs 17:06:02 [chipc]: let's list 'em 17:06:03 [chipc]: CLOUDSTACK-1934 17:06:16 [chipc]: nobody has taken it 17:06:19 [chipc]: so we need a fix 17:06:26 [chipc]: CLOUDSTACK-1971 17:06:39 [chipc]: Prachi is looking into that one 17:06:46 [chipc]: CLOUDSTACK-1978 17:07:03 [chipc]: unassigned as well... 17:07:09 [chipc]: but I'lll ping Hugo about it 17:07:17 [chipc]: CLOUDSTACK-1987 17:07:25 [chipc]: unassigned 17:07:32 [chipc]: CLOUDSTACK-1988 17:07:46 [chipc]: Likitha has that one 17:07:54 [chipc]: so that's the list of the bug's I'm tracking 17:08:01 [chipc]: packaging for RPM's is "done" 17:08:09 [jzb]: chipc: when did that come in? 17:08:18 [chipc]: jzb: what? 17:08:24 [jzb]: chipc: RPMs 17:08:46 [chipc]: Hugo told be in the ML that we were done with RPM packaging last week I think 17:08:48 [jzb]: ok 17:08:54 [chipc]: or over the weekend 17:09:09 [jzb]: what's the state of debian packages? 17:09:11 [chipc]: widodh told me he's done with DEB packaging as well, and anything outstanding is new bug to him 17:09:19 [chipc]: again, that was in the last day or so 17:09:31 [jzb]: Hm. OK, I tried doing debs yesterday and had no joy 17:09:33 [jzb]: I'll retry 17:09:39 [chipc]: he knocked out the last couple of obviously deb packaging related bugs 17:09:49 [chipc]: jzb: please do, and open blockers if you can't get it to work 17:10:03 [jzb]: yep 17:10:16 [chipc]: so those bugs, plus the word from you (jzb = you) on the release notes 17:10:24 [chipc]: then I think we are ready 17:10:31 [chipc]: so EOF on the overview 17:10:39 [jzb]: chipc: OK, shall we talk release notes now or wait for docs? 17:10:54 [chipc]: docs sounds like a good topic 17:10:56 [chipc]: for that 17:11:01 [jzb]: OK # 3. Active Feature Release: QA Status # 17:11:33 [jzb]: sudhap: have some good news for us on QA status? 17:11:46 [sudhap]: jzb:QA is done with testing 17:11:54 [sudhap]: only outstanding issues need to be closed 17:11:56 [chipc]: sudhap: great work to everyone btw 17:12:09 [sudhap]: testing is not active on 41 as far as I can tell 17:12:31 [sudhap]: chipc:thanks 17:12:39 [chipc]: sedhap: agreed that I think we are set with testing... at least beyond retest of the final bugs 17:12:56 [jzb]: OK 17:12:56 [sudhap]: I am reviewing outstanding resolved new and improvements and trying to see what is outstanding 17:13:18 [sudhap]: only few items left to be closed 17:13:25 [sudhap]: following up on those and closing them 17:13:39 [sudhap]: through JIRA tickets 17:14:02 [sudhap]: will be done in a day or two unless some QA work is pending but mostly it is just confirmation as work has been done 17:14:17 [sudhap]: if owner can review and close them it would be clean 17:14:46 [sudhap]: EOF on overall QA unless someone else bring up other concerns 17:15:01 [jzb]: sudhap: thanks! # 4. Active Feature Release: Docs Status # 17:15:39 [jzb]: OK, the biggie here is release notes 17:15:54 [jzb]: the good news is that I've made pretty good progress on the 4.0 -> 4.1 upgrade 17:16:09 [jzb]: also, getting closer on getting the API info 17:16:25 [jzb]: Alena has been very helpful on that, I just need to figure out the appropriate class path and see if that works. 17:16:54 [jzb]: the bad news is that there's still a fair amount to do on the 4.0 -> upgrade since the RPM procedure isn't documented elsewhere AFAIK 17:17:02 [jzb]: and we'll need to review the release notes heavily once they're complete 17:17:31 [ke4qqq]: jzb: I can either provide steps or perhaps pick up docs tomorrow 17:18:01 [jzb]: ke4qqq: thanks 17:18:16 [jzb]: we still have a few incomplete feature docs for 4.1.0 as well 17:18:24 [sangeetha]: This is regarding IPV6 templates ... 17:18:31 [chipc]: jzb: do you happen to have the list? 17:18:39 [jzb]: they're not blockers, though _ I guess 17:18:41 [jzb]: CLOUDSTACK-827 17:18:50 [jzb]: unassigned 17:18:58 [jzb]: CLOUDSTACK-862 17:19:03 [chipc]: jzb: I'd not want them to block, but that does suck 17
Summary of IRC meeting in #cloudstack-meeting, Wed Apr 24 17:04:18 2013
Members present: animesh, jzb Meeting summary: 1. Preface 2. Active Feature Release 3. Active Feature Release: Doc Status 4. Active Feature Release: Additional Issues? 5. Active Bug-Fix Release 6. Master Branch 7. Infra 8. Other Issues? IRC log follows: # 1. Preface # # 2. Active Feature Release # 17:05:03 [jzb]: OK, any report on the 4.1.0 release? 17:05:18 [jzb]: I know Chip mentioned we have problems with packaging. 17:05:54 [jzb]: and we had another report of trouble upgrading from 2.2.14 to 4.1.0 17:06:01 [jzb]: anything else? 17:06:39 [animesh]: I am 17:07:16 [jzb]: OK, I guess that's all on the active feature release topic. 17:09:14 [jzb]: OK next topic # 3. Active Feature Release: Doc Status # 17:09:46 [jzb]: Just a quick update - docs are more or less done for 4.1.0 unless anyone has a report of bugs that are show-stoppers 17:10:14 [jzb]: we still have a number of things that should have made it into 4.1.0, though so once we release 4.1.0 it'd be nice to wrap those up for 4.1.1 # 4. Active Feature Release: Additional Issues? # 17:10:47 [jzb]: any additional issues to report this week? 17:12:06 [jzb]: OK 17:12:07 [jzb]: next topic # 5. Active Bug-Fix Release # 17:12:29 [jzb]: And the status on this is... poised for release! Yay! 17:12:36 [animesh]: Cool 17:12:37 [jzb]: No further releases expected in 4.0.x series. 17:12:51 [jzb]: Once 4.1.0 is released, this will become the 4.1.1 topic. # 6. Master Branch # 17:13:21 [jzb]: animesh: I believe this one is yours. 17:13:29 [jzb]: anything to discuss or report this week? 17:13:51 [animesh]: I need to summarize 4 month-6 month thread by tomorrow 17:14:29 [animesh]: Then based on the consensus finalize 4.2 release dates, set up release page , dashboard etc 17:14:51 [jzb]: animesh: do we seem to have consensus? 17:15:31 [animesh]: I am not sure of that I do see a pattern as better automation being the solution to avoid reliance on manual QA 17:16:06 [animesh]: I will wait today for more input to come in 17:17:22 [jzb]: OK 17:17:29 [animesh]: nothing else on master # 7. Infra # 17:17:51 [jzb]: any infra topics this week? 17:18:16 [animesh]: I was granted the permission to create shared filter and add group recipients 17:18:29 [jzb]: animesh: in Jira? 17:18:38 [animesh]: Yes in Apache JIRA 17:18:58 [jzb]: OK 17:19:12 [animesh]: This was follow on to don't assign defects thread. I want to set up filters based on modules that folks can subscribe to 17:19:26 [jzb]: animesh: ah, groovy 17:19:41 [animesh]: And possibly send out regular emails to dev mailing list on module basis 17:20:11 [jzb]: I'd like to see that. 17:20:50 [jzb]: anything else? 17:20:58 [animesh]: If it works we should refine our module list some of them are too generic 17:21:05 [jzb]: animesh: example? 17:21:19 [animesh]: Like Management Server 17:21:49 [animesh]: By modules I mean component term in JIRA 17:22:41 [animesh]: Thats all from my side 17:22:44 [jzb]: I see # 8. Other Issues? # 17:23:56 [jzb]: any other issues to talk about this week, folks? 17:25:07 [animesh]: None 17:25:11 [jzb]: OK, I'll wrap it up then.
Summary of IRC meeting in #cloudstack-meeting, Wed May 1 17:05:15 2013
Members present: animesh, chipc Meeting summary: 1. Preface 2. 4.1.0 Release 3. 4.2.0 Release a. https://cwiki.apache.org/confluence/display/CLOUDSTACK/Cloudstack+4.2+Release (chipc, 3) b. https://cwiki.apache.org/confluence/display/CLOUDSTACK/Current+Maintainers+Per+Component (chipc, 3) 4. Other Topics IRC log follows: # 1. Preface # 17:05:16 [chipc]: ASFBot: meeting start # 2. 4.1.0 Release # 17:05:52 [chipc]: Here's where we stand on 4.1.0: we still have upgrade issues to re-test 17:06:10 [chipc]: and I believe there is an issue I saw on the ML for another upgrade problem, but no bug ID 17:06:17 [chipc]: I'll have to get back through the list to see 17:07:00 [chipc]: it's a little difficult to get through these problems, since they are reported by someone in a very different timezone than the devs that can help fix the problems 17:07:09 [chipc]: and today being a holiday in the EU is delaying retesting 17:07:22 [chipc]: so that's unfortunate, but it is what it is 17:07:30 [chipc]: any other 4.1.0 topics? 17:07:52 [chipc]: going once 17:08:09 [chipc]: twice 17:08:30 [chipc]: sold... moving on # 3. 4.2.0 Release # 17:08:46 [chipc]: animesh: have anything to share? 17:09:00 [animesh]: Ok so last week we concluded to keep 4.2 on 4 month schedule 17:09:07 [chipc]: yes 17:09:07 [animesh]: I have updated the 4.2 release page 17:09:30 [animesh]: I have setup a bunch of filters based on open issues for specific components 17:09:38 [chipc]: #info https://cwiki.apache.org/confluence/display/CLOUDSTACK/Cloudstack+4.2+Release 17:09:52 [chipc]: animesh: did you share those filters with the ML? 17:10:02 [animesh]: I am updating the current maintainers page with subscription links to these filters 17:10:30 [animesh]: Folks should be able to setup personal subscription for the components they are interested in 17:11:15 [chipc]: #info https://cwiki.apache.org/confluence/display/CLOUDSTACK/Current+Maintainers+Per+Component 17:11:15 [animesh]: I would have like to add cloudstack dev mailing list to receive direct emails for the component issues 17:11:22 [chipc]: looks good! 17:11:39 [animesh]: I was working with infra to see if that could be done, but it is not supported 17:12:00 [chipc]: what would that mean? some sort of weekly or daily email from each component? 17:12:15 [animesh]: I will setup my own personal subscriptions and set up mail client rule to forward the component issues to dev mailing list 17:12:39 [animesh]: Next I will set up dashboard for 4.2 17:13:01 [chipc]: but what would it look like coming to dev@? 17:13:30 [animesh]: I will send out an email to dev later today on the filters and subscription 17:13:37 [chipc]: ok, thx 17:14:06 [animesh]: I will open up a discussion on dev on how often we would like to see the component issue emails. may be a week 17:15:00 [chipc]: perhaps a different approach could be to have issues@cloudstack.a.o emails get the component in the subject line? 17:15:15 [chipc]: I'll reply with that idea when you start the DISCUSS thread 17:15:17 [chipc]: ok - so anything else on 4.2.0? 17:15:39 [animesh]: Yes the component description shows up in subject line 17:16:30 [animesh]: That's all that I know, let me know if I am missing anything 17:16:41 [chipc]: well, I guess that's it then ;-) 17:16:54 [chipc]: ok... next topic # 4. Other Topics # 17:17:21 [chipc]: Since I think it's just animesh and I in the meeting... generalized this section 17:17:30 [chipc]: anyone have anything else to discuss? 17:18:07 [chipc]: ok then... I guess that;'s it. Thanks for joining Animesh 17:18:15 [chipc]: ACTION wishes others made it
Summary of IRC meeting in #cloudstack-meeting, Wed May 15 17:18:37 2013
Members present: chiradeep, topcloud, animesh__, rajesh_battala, sudhap Meeting summary: 1. Preface 2. ACS 41 release 3. ACS 42 a. Animesh to send a reminder to dev mailing list today (animesh__, 3) 4. general Actions: - Animesh to send a reminder to dev mailing list today (animesh__, 17:24:47) IRC log follows: # 1. Preface # 17:18:38 [animesh__]: ASFBot: meeting start # 2. ACS 41 release # 17:19:28 [rajesh_battala]: Am here 17:19:41 [animesh__]: Any one around to report on ACS 41 progress 17:21:44 [animesh__]: We have 3 unresolved issues at this time 17:22:59 [animesh__]: moving on to 4.2 # 3. ACS 42 # 17:23:51 [animesh__]: The unresolved defect count has been increasing 17:24:29 [animesh__]: and many feature issues are still open 17:24:47 [animesh__]: #action Animesh to send a reminder to dev mailing list today 17:25:14 [animesh__]: Sudha any update from QA? 17:25:21 [topcloud]: animesh__: did we already do a design freeze like in 4.1? 17:25:53 [chiradeep]: ACTION note-to-self, update my bug status 17:26:36 [sudhap]: animesh: progressing on new feature validation - there are a few features which are not taken up by anyone for QA Task. Will go over them in JIRA and ask community if someone can volunteer 17:26:39 [animesh__]: topcloud: can you clarify on design freeze 17:27:21 [animesh__]: I had moved out all unassigned feature / enhancement items that were not claimed last week 17:27:46 [topcloud]: animesh__: I think in 4.1, chip actually had a date where proposed feature is set for 4.1. 17:27:53 [topcloud]: that's before the code freeze. 17:28:32 [sudhap]: animesh, topcloud: I think we passed that stage given code freeze is 5/31 17:28:36 [animesh__]: I am using Chip's template for 4.2 release 17:29:14 [topcloud]: sudhap: I think so too but it's good to make it clear to the community. 17:29:15 [animesh__]: I think it is the deadline for claiming unassigned features that we have already passed 17:29:29 [topcloud]: ic. 17:29:36 [animesh__]: I had sent a reminder to community last week 17:29:36 [topcloud]: makes sense. 17:30:32 [animesh__]: Any other topics for 4.2 17:30:44 [sudhap]: Also we should move unclaimed 4.1 defects to 4.2 17:31:22 [animesh__]: should we wait for 4.1 to be released and then move the defects 17:32:29 [sudhap]: I will publish upgrade plan i.e compatiblity matrix - sent one for 4.1 but we completely miss 2.2.x upgrade path which pose lot of issues 17:33:01 [animesh__]: yes the 4.1 QA plan covered testing from 4.0 to 4.1 only 17:33:29 [sudhap]: I think chip is looking only for blocker and criticals for 4.1 - anyway it is better to wait till it goes out 17:34:21 [animesh__]: Yes I know we are looking at blockers and critical only but it is possible for an issue to get bumped up if it was overlooked 17:34:44 [animesh__]: so we should wait for 41 to be released 17:34:59 [sudhap]: animesh:yes - for some reason we thought that upgrade path is not required - no one also raised any concern as well - we will correct it for 4.2 17:35:14 [sudhap]: ok 17:35:29 [sudhap]: there are 50+ critical defects in 4.2 17:35:44 [sudhap]: hope these will be fixed soon 17:35:59 [animesh__]: I will send a 42 reminder today 17:36:15 [animesh__]: anything else on ACS 42 17:36:24 [sudhap]: I will post QA milestones for 4.2 # 4. general # 17:37:36 [animesh__]: Does anyone have anything else to report 17:38:29 [animesh__]: ok so lets conclude the meeting
