Github user koushik-das commented on the pull request:
https://github.com/apache/cloudstack/pull/780#issuecomment-199254175
@DaanHoogland I don't see any reason for closing master in this case. If an
issue is noticed after a merge, it definitely needs to be tracked and fixed.
Releasing a branch can definitely be blocked if the issues (particularly
regressions) are not addressed but I don't see any reason to close master for
other commits. I think that closing master makes sense only if build is broken
or there is a blocking regression introduced after the last release.
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
