Hi all, Lots of work has been done yesterday! PRs were reviewed, tested, merged, some were improved and then tested. Nice results in translations as well. The channel on Slack proved to be a great way to collaborate remotely.
Important: please rebase! ========================= Now that many issues have been resolved again, we need to rebase the open pull requests with current master. I'm testing a lot of PRs and it's a waste of time to realise failures are due to an outdated branch. Now that most tests work on master, I'd like to see them succeed in PRs as well to avoid missing regression. PRs for 4.6? ============ I just wish I could use GitHub labels. @ke4qqq help! ;-) If there are PRs you want to be considered for 4.6, please: - Rebase the PR against current master (and keep it in sync) - Let me or Rajani know about it Generally speaking, bug fixes and small improvements will be considered. Large refactors or large features probably won't. Blockers ========= We have 3 blockers in Jira: 1) CentOS 7 - systemd-tmpfiles - Operation not permitted This is about the CentOS 7 packaging of the Management Server. https://issues.apache.org/jira/browse/CLOUDSTACK-8812 ==> Paul is working on this (he confirmed yesterday that he is still working on it). Let us know if you need help, Paul! 2) VR password server broken https://issues.apache.org/jira/browse/CLOUDSTACK-8957 ==> Rohit is working on this, or not? No recent update. Please unassign if someone else needs to take over. Do you need help Rohit? 3) Can't create template or volume from snapshot - "Are you sure you got the right type of server?" https://issues.apache.org/jira/browse/CLOUDSTACK-8964 ==> Lots of people working together ==> PR https://github.com/apache/cloudstack/pull/954 I'm running some tests as we speak. This one we should be able to complete soon. Note: There might be some critical issues as well that people may want to work on: https://issues.apache.org/jira/browse/CLOUDSTACK-8918?filter=12332940 (please login) If are working on something for 4.6, let me know about it. As you can see, if an issue is not in Jira or there is no PR, we’re unaware and probably won’t include it in 4.6. So, make sure Jira is up to date. Please keep testing master while we’re working towards 4.6RC1. It’s going to be a great release. Let’s keep up the good work! Regards, Remi
