cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From mike-tutkowski <>
Subject [GitHub] cloudstack pull request: Changed variable s_logger to non-static a...
Date Tue, 15 Sep 2015 13:58:04 GMT
Github user mike-tutkowski commented on the pull request:
    I could say this again, but it doesn't seem like it's a popular opinion with regards to
CloudStack development:
    If we are really "late in the game" with regards to the 4.6 release, then probably half
or more of the PRs we put into the codebase should not be going in at this point (they should
be going into 4.7).
    The way most software development I've been involved with over the past 17 years works
is that defect and enhancement tickets are prioritized by a cross-functional team (it doesn't
have to be cross functional, though, for CS).
    These defect/enhancement priorities along with the stage at which we are in development
(i.e. how close we are to our release deadline) inform what actually goes into the current
release and what is postponed to the next release.
    We have a habit with CS of just continuously churning the codebase up until the very last
    If we had an awesome suite of regression tests, we might be able to get away with that.
I saw "we might," but - in reality - it's still not a good idea to do that. Many defects don't
show up until the code has "soaked" over long periods of time and we don't have any way to
protect against that the way we develop and test CS code.

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message