Versions Compared

Old Version 13

changes.mady.by.user Mathias Mullins

Saved on

compared with

New Version 14

changes.mady.by.user Mathias Mullins

Saved on

Key

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

...

Animesh Chaturvedi the release manager for 4.2 and is tracking the current status of the release. Testing, bug fix work, and documentation should be targeted to complete by 7/28. Release is still on schedule to release by 8/19.Link and quote to be added after Animesh's night should be out tonight

As for bugs here is a summary for this week:

Bugs

This Week

 

 

 

Two Week Ago

 

 

 

 

Blocker

Critical

Major

Total

Blocker

Critical

Major

Total

Incoming

8

10

28

50

11

34

24

72

Outgoing

26

23

34

86

26

30

40

100

Open Unassigned

7

49

129

222

6

49

119

184

Open Total

25

84

232

403

25

80

218

385

Swift Support in 4.2

On July 3rd, Edison Su reported that support for Swift is broken due to the object store refactor. There's been a fair amount of discussion on how an extant feature could be broken without being exposed via testing, and what should be done about it at this stage.

...

Since the cloudstack project has moved to ASF, the suggestion is to move
from com.cloud packages to org.apache java packages .( https://issues.apache.org/jira/browse/CLOUDSTACK-212)

As you might be realize, this is pretty big change. And merging this
changes with a continuously updating master is non-trivial. So, here is the
planned strategy after discussion over IRC. I am starting this thread to
inform and know everyone's opinions.

1. I will be pushing code with new packages on branch "namespacechanges"
and will notify on this thread as each refactored module is pushed.

2. There will be a freeze on master branch commits for some time in which
"namespacechanges" will be applied to master. I suggest the date to be 20th
July.

3. All the branch-owner updates their branch for reflect new packages. It
was suggested that branch owners can look into the "namespacechanges"
branch as it grows and start doing the package changes early, although it
depends on branch-owners.

In-Development Release Naming

While we are still hard at work at getting 4.2 out the ready and out to the world, John Burwell has purposed moving to release naming until a release has gotten to feature freeze and it can be judged on what the semantic version number change should be. There's been a lot of discussion on this topic. We would probably look to start this in the next release if it can come to a vote.

Since we have adopted Semantic Versioning 1, it seems odd that we designate a release version before the final set of enhancements/fixes has been identified. For example, the release proceeding 4.2 may contain no backwards compatible API changes to be 4.3. Conversely, we may decide during the development cycle, as a community, to accept a non-backwards compatible change which would bump the version to 5.0.0. As such, it is difficult to know in advance what the proper semantic version number will be at when the work is released. We run the risk of confusing our users if we start calling a pending release say 4.3.0, and accept a change mid-cycle that will bump it to 5.0.0. To address this potential issue, I proposed that we refer to releases by a codename until feature freeze when we understand the complete scope of change and can apply the correct semantic version number. I further propose we codename the release directly proceeding 4.2 "Gamma Rays" or "Gamma Rays Gonna Get Ya".

CloudStack Planet

What's going on in the CloudStack community? While all the discussion happens on the mailing lists, we also encourage members of the CloudStack community to share what they're working on their blogs. In this section, you'll find posts by Apache CloudStack community members and interesting news that's relevant to Apache CloudStack.

...

Joe Brockmeier talks a bit about Gene Kim's keynote at the CloudStack Collaboration Conference, "Why Every Company Needs DevOps Now."

Hackathon Storage Group Puts Out Discussion and Proposal

John Burwell who led the storage discussion group during the CloudStack Collaboration Conference Hackathon put out the first group discussion on the future needs and a proposal on how to better define storage for future versions of CloudStack. Read the and participate in the discussion and weigh-in on the proposal.

Interview with The Cloudcast (.net)

...

New Committers and PMC Members

...