Page History

...

Chip opened CLOUDSTACK-3400 as a blocker against 4.2 until Swift support is fixed. Discussion about the bug continues.

Coding Convention Reminder

As open source projects mature and add new participants, it's occasionally necessary to send a gentle reminder of accepted conventions in the community. For example, Alex Huang opened a discussion about the CloudStack coding conventions on July 2nd, saying "Our [coding
conventions|https://cwiki.apache.org/confluence/display/CLOUDSTACK/Coding+conventions] have been going all over the place recently. Please take a look."

He also proposed extending the 120 column limit to 180 columns.

I recently was reading the following code. If it followed even our current coding conventions, this would have been 11 lines but it ends up to be 23 lines,
more than doubled. The whole file was like this. Just thinking about all the extra scrolling I have to do makes my cts act up. We are in the 21st century
and using wide screen lcd monitors. Let's not format our code to fit 80 column amber text screens please!

What's worse is I've found that some people are actively breaking existing source code to 80 columns, causing a bunch of unnecessary merge activities.

For those folks who use Eclipse Alex has checked in his Eclipse profile to tools/eclipse/eclipse.epf. It will help with a number of issues, such as removing trailing white space, reformats edited portions of the file using the current formatting rules, and more.

Changing Bug Severity

Prasanna Santhanam noted that some bugs have changed severity without any reason given. Any time a change of this sort of significance is made in Jira, some reason should be given so that other users can have some idea why the change was made without having to track down the person responsible and ask.

Prasanna asks:

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 Added}

Chip replied:

+1 with an added "d)":

d) needs to be considered a release blocker for a legal, security or
trademark reason

4.2 Release

Progress on 4.1.1 Release

...

New Committers and PMC Members

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