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 [email protected] 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
