Page History

...

We are now just 3 weeks from ACS 4.2 code freeze on 7/29. We have around 400 open defects with 100+ blockers and critical and I expect another 200 new defects to come in. As a community we have been fixing roughly 100 defects per week, in order to clear up our backlog I request you to help out on aggressively fixing the issues. The unassigned issue list is available at http://s.apache.org/BlH/^{Image Removed}. When you fix a bug in 4.2 please make sure it is also fixed in master.

Given the debate on system template changes in last few days of 4.1 requiring big testing effort and potential regression, I would like to see that as community we lock down system templates for 4.2 pretty soon. If any changes are needed we should call it out now and get them resolved.

As for bugs here is a summary for this week:

Bugs	This Week				Last Week
	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

The status for features or improvement is depicted in table below

New Features / Improvements	Today	Last Week
Closed	10	10
Resolved	59	57
In Progress	11	13
Reopened	1	1
Ready To Review	1	1
Open	20	20
Total	102	102

...

Can the bug reporters please mention the
reason as to how something :

a) blocks movement on the feature/installation/cloudstack in general
b) affects deployment and does not have workarounds via the API
c) troubleshooting done with respect to a and b.

Here's some light reading on how to have bugs resolved faster: http://www.chiark.greenend.org.uk/~sgtatham/bugs.html^{Image Removed}

Chip replied:

...

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^{Image Removed})

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.

...