Several major discussions this week, summarized below. Note that this is only a fraction of the activity in the project. For a full overview of project activity, you may want to subscribe to dev@cloudstack.apache.org.
4.1.0 vote is currently on hold pending two bugs. CLOUDSTACK-2309 reported on May 2. Also CLOUDSTACK-2218 has been reopened. Both are unassigned and need someone to jump in quickly to help move these forward.
To better help communicate about security related matters, announce security concerns, and determine additional security needs for CloudStack, a new mailing list Security@cloudstack.apache.org is being setup. You can subscribe by e-mailing security-subscribe@cloudstack.apache.org.
If you have an event you wanted added here, please send to the marketing@cloudstack.apache.org or see how to contribute to the news below.
Checking in on the upcoming 4.2.0 release, we have removed a few bugs over the past week:
Last week we had 11 blocker bugs for 4.2.0. We had no new blocker bugs for 4.2.0 this week.
Last week we had 40 critical bugs for 4.2.0. This week, we have 38 critical bugs for 4.2.0, closing 2 more out.
Last week we had 273 major bugs for 4.2.0. This week, we have 254 major bugs for 4.2.0, closing 19 out.
Last week we had 37 minor bugs for 4.2.0. This week we have 28 minor bugs for 4.2.0, closing 9 out.
30 bugs in the last week closed out. This progress is a community win for everyone!
Clayton Weise was announced as a new committer on April 30, 2013. Congratulations!
Want to keep reading the CloudStack Weekly News? Many hands make light work, but having only one editor means getting the weekly news out every week is a "best effort" activity. A healthy community publication needs several contributors to ensure weekly issues go out on time.
If you have an event, discussion, or other item to contribute to the Weekly News, you can add it directly to the wiki by editing the issue you want your item to appear in. (The next week's issue is created before the current issue is published - so at any time there should be at least one issue ready to edit.)
Alternatively, you can send a note to the marketing@cloudstack.apache.org mailing list with a subject including NEWS: description of topic or email the newsletter editor directly (jzb at apache.org), again with the subject NEWS: description of topic. Please include a link to the discussion in the mailing list archive or Web page with details of the event, etc.