cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daan Hoogland <>
Subject Re: [VOTE][ACS44]Apache CloudStack 4.4.1 RC 3 in branch 4.4-RC20141014T2316
Date Mon, 20 Oct 2014 07:48:05 GMT
take a look in I changed it to not have to revert RCs in case
they didn't pass. Also if issues are only packaging we could stay on the
branch. I saw this practice wasn't promoted to master and hence 4.5 but i
think it should. Unless we go with your proposal of not snapshotting of

On Mon, Oct 20, 2014 at 9:41 AM, Rohit Yadav <>

> Hi Daan,
> > On 20-Oct-2014, at 1:02 pm, Daan Hoogland <>
> wrote:
> >
> > no, the release is on that branch not on the 4.4 branch. We could rename
> > the branch if needed. putting the tag on 4.4 would make it either a
> > 4.4.1-SNAPSHOT or a 4.4.2-SNAPSHOT depending on where on the branch we
> put
> > the tag.
> If you look at other branches, 4.2, 4.3 etc all the tagged releases are
> done on the branch; there is no separate release branch like in this case
> 4.4-RC20141014T2316. It’s just a matter of ease here, I can always git
> fetch and checkout a tag, but historically we’ve put tags on the release
> branch that we cut out.
> I also wanted to discuss why we add -SNAPSHOT at all, what’s the harm in
> say keep the next version to 4.4.2 (if we have 4.4.2 in future)? This
> diverges code (in git terms) a lot, why not just switch to the next
> version? When building rpms or debs (in changelog), we can still add a
> suffix but those changes would introduce minimal divergence.
> Regards,
> Rohit Yadav
> Software Architect, ShapeBlue
> M. +91 88 262 30892 |
> Blog: | Twitter: @_bhaisaab
> Find out more about ShapeBlue and our range of CloudStack related services
> IaaS Cloud Design & Build<
> CSForge – rapid IaaS deployment framework<>
> CloudStack Consulting<>
> CloudStack Infrastructure Support<
> CloudStack Bootcamp Training Courses<
> This email and any attachments to it may be confidential and are intended
> solely for the use of the individual to whom it is addressed. Any views or
> opinions expressed are solely those of the author and do not necessarily
> represent those of Shape Blue Ltd or related companies. If you are not the
> intended recipient of this email, you must neither take any action based
> upon its contents, nor copy or show it to anyone. Please contact the sender
> if you believe you have received this email in error. Shape Blue Ltd is a
> company incorporated in England & Wales. ShapeBlue Services India LLP is a
> company incorporated in India and is operated under license from Shape Blue
> Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil
> and is operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is
> a company registered by The Republic of South Africa and is traded under
> license from Shape Blue Ltd. ShapeBlue is a registered trademark.


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message