You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jclouds.apache.org by Nirmal Fernando <ni...@wso2.com> on 2014/02/06 07:12:53 UTC
How jclouds back-port changes to an already released version?
Hi All,
What's the procedure of doing this? Do you all create a new minor version?
--
Thanks & regards,
Nirmal
Senior Software Engineer- Platform Technologies Team, WSO2 Inc.
Mobile: +94715779733
Blog: http://nirmalfdo.blogspot.com/
Re: How jclouds back-port changes to an already released version?
Posted by Nirmal Fernando <ni...@wso2.com>.
Cool... thanks Andrew.
On Thu, Feb 6, 2014 at 11:57 AM, Andrew Gaul <ga...@apache.org> wrote:
> On Thu, Feb 06, 2014 at 11:42:53AM +0530, Nirmal Fernando wrote:
> > What's the procedure of doing this? Do you all create a new minor
> version?
>
> Yes. We cannot backport to a released version, e.g., 1.7.0, although we
> can backport to the release branch, e.g., 1.7.x, and release a new
> version, e.g., 1.7.1. Backporting usually refers to cherry-picking a
> commit from master/1.8.x into an older branch.
>
> --
> Andrew Gaul
> http://gaul.org/
>
--
Thanks & regards,
Nirmal
Senior Software Engineer- Platform Technologies Team, WSO2 Inc.
Mobile: +94715779733
Blog: http://nirmalfdo.blogspot.com/
Re: How jclouds back-port changes to an already released version?
Posted by Andrew Gaul <ga...@apache.org>.
On Thu, Feb 06, 2014 at 11:42:53AM +0530, Nirmal Fernando wrote:
> What's the procedure of doing this? Do you all create a new minor version?
Yes. We cannot backport to a released version, e.g., 1.7.0, although we
can backport to the release branch, e.g., 1.7.x, and release a new
version, e.g., 1.7.1. Backporting usually refers to cherry-picking a
commit from master/1.8.x into an older branch.
--
Andrew Gaul
http://gaul.org/