Hi Wido, Thank you for telling me that.
I remembered that Chip has sent how to control 4.1 release. http://markmail.org/message/qkkxycablpsmogsx https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.1+Release Chip, the commits I pushed into 4.1 were: - 2 patch commit for debian packaging issues - 9bc4393 for Japanese translations - 8faf845 for KVM OVS setup issue I'm sorry I should have send a patch request. But I'm sure first 3 are really release blockers. Regards, (2013/05/27 17:10), Wido den Hollander wrote:
Hi Hiroaki, I've noticed you pushed a couple of commits into both master and 4.1 without going through the patch request on the mailinglist. For example in 4.1: * 9bc43930b822a294c863e954bc5b39fc4b506f46 * 8faf845889b28157a2ecbd6e406d73a326b27756 When the 4.1 branch was frozen the agreement was/is that all commits into the 4.1 branch have to go through the mailinglist so Chip Childers can pick them up and cherry-pick them into the 4.1 branch. I see you made some good commits, but the 4.1 branch is actually frozen at this point. The Debian package fixes are very welcome though! But since we are in the process of voting for a 4.1 release we have to make sure nothing changes in the 4.1 branch. Maybe you weren't aware of this agreement, so that why I'm sending this to you. Thanks! Wido
