You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Welcome back to another exciting issue of the Apache CloudStack Weekly News. This week, 4.2.0 enters code freeze, 4.1.1 gets set for release, and some major discussions on the Apache CloudStack mailing lists, and much more.

Major Discussions

4.2 is Now in Code Freeze

The 4.2 release is now in code freeze as of 7/29/13. This means that only selected updates will be done on critical and blocker bugs only. This is also a time to work on documentation and preparing for the first RC on 8/19/2013. Animesh Chaturvedi detailed out the process during code freeze.

...
Given the high number of blocker and critical and that QA is still filing many defects I will follow what Chip did for 4.1 1. Up until when we cut the first RC on (2013-08-19) committers should continue to check in fixes to 4.2 branch for blocker and critical issues. Please do any fixes as cleanly as possible (i.e., squash related commits and make sure to avoid messy merge commits as much as possible).

For Contributors if you have a fix that needs to go into 4.2, please email the list with the subject tag ACS42 and note the review that contains the patch. I'll pick whichever I can, but will also rely on others with commit rights to make it efficient.

I will review all commits going into that branch, and will revert anything that's outside the scope of that I outlined above (unless there is a discussion and consensus on this list to include something else).
...

4.2 Block and QA Issue Closure

Sudha Ponnaganti put together a list of the the current blocker and critical issues that need to be reviewed. If you have issues that have been resolved please review, test, and close out please.

4.1.1 Release Has Been Voted On

Second round of voting was started on 7/25 after a new cut of the RC was compiled. The release has been tested and voted on. Chip Childers put out the results. Chip will be publishing the release this week.

...
Results:

+1 binding: chip, marcus, wido, alex, / non-binding: simon
-1 non-binding: ove, nicolas

Based on those results, I'll move forward with publishing the release
now.

-chip

Documentation Review and Input

As the final code products are now final, the documentation is well underway and many sections are coming available for review. Please take the time to review, comment and file doc bugs when you find issues (yes, even documents have bugs). The document team are using the DOC tag to keep everyone up to date. Here are some docs that Radhika Puthiyetath have posted for review:
*15.7. IP Reservation in Isolated Guest Networks - https://issues.apache.org/jira/browse/CLOUDSTACK-850
*15.13. Adding Multiple IP Ranges - https://issues.apache.org/jira/browse/CLOUDSTACK-847

Bylaws change for Committer and PMC Member Nomination

To make the process of allowing for nomination of Committers and PMC members into the CloudStack community, Chip Childers has started a discussion on changing the bylaws to change the voting process of the PMC Group from a lazy consensus to a majority process. Join in the discussion.

As it stands now, we currently use a "Lazy Consensus" model (yes Noah, I know we didn't define that term correctly as of now, but I think that's a different discussion). We currently have that term defined as:

Lazy Consensus - Lazy consensus requires 3 binding +1 votes and no binding -1 votes.

I'd like to propose that we change the PMC and Committer voting rule to use the Lazy 2/3 Majority approach defined as:

Lazy 2/3 majority votes requires at least 3 binding votes and twice as many binding +1 votes as binding -1 votes.
...

CloudStack Planet

Events

New Committers and PMC Members

No new committers or PMC members have been announced in the last newsletter period.

  • No labels