This is why I introduced the branch on rc policy. I discussed it with
David this morning and we concluded that it is missing a merge back.
That doesn't mean that on each upgrade an emtpy upgrade path is
needed.
On Tue, Nov 18, 2014 at 5:11 PM, Rohit Yadav wrote:
> This broke deploydb and since we
This broke deploydb and since we may not get time today/tomorrow I had to
revert. Our 4.3 release manager is well informed about this.
I hope when we change the version we should make sure CloudStack builds, and
normal operations such as deploydb should work. We should re-revert this once
we’ve
4.3.1 is out. is this really what we want, Rohit? seems this revert
shouldn't happen.
On Tue, Nov 18, 2014 at 11:35 AM, wrote:
> Repository: cloudstack
> Updated Branches:
> refs/heads/4.3 e615f218a -> e6d00bcc6
>
>
> Revert "Updating pom.xml version numbers for release 4.3.2-SNAPSHOT"
>
> Thi
