Versions Compared

Old Version 8

changes.mady.by.user Mathias Mullins

Saved on

compared with

New Version 9

changes.mady.by.user Mathias Mullins

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

...that sweeping changes like this (or architectural changes as well) are best done early in a release cycle. The challenge we've run into here is that while 4.2 work is proceeding, master is open for 4.3 changes (and there is a preference that if something big is going to come in, nows the time to do it).

4.1.1 Release Candidate Vote is Now Open

4.1.1 patch release has been in the works for a while now and has quite a few fixes in it since the release of 4.1.0 on June 5th. The release candidate was cut on Monday and the Vote is now open until Saturday. Please provide your testing results and vote.

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.
...

Possibly Ending the IRC Chats

After low attendance in weekly IRC chats, Joe Brockmeier has raised the question about the need for regular IRC chats. IRC chats have been in place for a long time with the community. Make sure to stay involved with the discussion and let your voice be heard.

How Your Coding May Affect Others

Brian Federle noticed when working on the GUI code in Master recently that the tab style had changed. This started a large rebase and merge of the UI code of other developers in the community. While the original commit had the best intention and was committed correctly for 4.3, the review and commit were done within a short time frame and didn't give the community much time to see it and understand the impact. Make sure to communicate and be aware of what impacts your code might have on others working on the same objects as you.

Chip Childers pointed out:

...that sweeping changes like this (or architectural changes as well) are best done early in a release cycle. The challenge we've run into here is that while 4.2 work is proceeding, master is open for 4.3 changes (and there is a preference that if something big is going to come in, nows the time to do it).

CloudStack Planet

Events

...