Re: [VOTE] Simplify CloudMonkey's branching/maintenance process

2014-12-11 Thread Rohit Yadav 

Hi everyone,

Thanks for voting and for your feedback. The voting concludes today
after 72 hours since the initial email, we've 10 +1s, 0 -1s and 0 +0s
and with at least 3 +1s from PMC members the voting passes.

I'll go ahead and clean old branches, update release process wiki for
CloudMonkey and we'll follow the following process:

- master is the only main working branch
- branch based workflow where the aim is to make sure master is always
stable
- tags and rolling releases out of master
- CloudMonkey releases should be backward compatible with clean upgrades

On Wednesday 10 December 2014 10:17 PM, Suresh Sadhu wrote:

+1

-Original Message-
From: Rajani Karuturi [mailto:raj...@apache.org]
Sent: 10 December 2014 06:20
To: dev@cloudstack.apache.org
Subject: Re: [VOTE] Simplify CloudMonkey's branching/maintenance process

+1


On Tue, Dec 9, 2014 at 18:55 PM, Rohit Yadav 
wrote:

Hi,

CloudMonkey's git repo history is mostly linear and the work on master is 
simply getting synced on 5.3 branch. I want to ask the community if anyone has 
any objections on just keeping master as the working branch and have branches 
when they are needed (say documentation, feature work
etc) and once they are merged they can be removed. We have git tags to identify 
past release so is it also alright with everyone to remove the support branches 
such as 5.3/5.2 etc.

This way we will have:
- one main working branch (master)
- branch based workflow: feature branches for doing feature work, pull requests 
or reviewboard for bugfixes for non-committers
- master is aimed to remain stable
- master will have its own TravisCI and tests (in upcoming weeks)
- CloudMonkey aims for progressive/rolling releases that are backward 
compatible with older releases and have clean upgrades

For this please vote with your comments/suggestions;

+1  approve
+0  no opinion
-1  disapprove (and reason why)

Regards,
Rohit Yadav
Software Architect, ShapeBlue
M. +91 8826230892 | rohit.ya...@shapeblue.com
Blog: bhaisaab.org | Twitter: @_bhaisaab PS. If you see any footer below, I did 
not add it :) Find out more about ShapeBlue and our range of CloudStack related 
services

IaaS Cloud Design & Build<http://shapeblue.com/iaas-cloud-design-and-build//



CSForge – rapid IaaS deployment framework<http://shapeblue.com/csforge/>
CloudStack Consulting<http://shapeblue.com/cloudstack-consultancy/>
CloudStack Software Engineering<http://shapeblue.com/cloudstack-software-
engineering/>
CloudStack Infrastructure Support<http://shapeblue.com/ 
cloudstack-infrastructure-support/>
CloudStack Bootcamp Training Courses<http://shapeblue.com/ cloudstack-training/>

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.



--
Sent from Windows Phone



--
Regards,
Rohit Yadav
Software Architect, ShapeBlue
M. +91 8826230892 | rohit.ya...@shapeblue.com
Blog: bhaisaab.org | Twitter: @_bhaisaab
PS. If you see any footer below, I did not add it :)
Find out more about ShapeBlue and our range of CloudStack related services

IaaS Cloud Design & Build<http://shapeblue.com/iaas-cloud-design-and-build//>
CSForge – rapid IaaS deployment framework<http://shapeblue.com/csforge/>
CloudStack Consulting<http://shapeblue.com/cloudstack-consultancy/>
CloudStack Software 
Engineering<http://shapeblue.com/cloudstack-software-engineering/>
CloudStack Infrastructure 
Support<http://shapeblue.com/cloudstack-infrastructure-support/>
CloudStack Bootcamp Training Courses<http://shapeblue.com/cloudstack-training/>

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 h

RE: [VOTE] Simplify CloudMonkey's branching/maintenance process

2014-12-10 Thread Suresh Sadhu 
+1

-Original Message-
From: Rajani Karuturi [mailto:raj...@apache.org] 
Sent: 10 December 2014 06:20
To: dev@cloudstack.apache.org
Subject: Re: [VOTE] Simplify CloudMonkey's branching/maintenance process

+1


On Tue, Dec 9, 2014 at 18:55 PM, Rohit Yadav 
wrote:

Hi,

CloudMonkey's git repo history is mostly linear and the work on master is 
simply getting synced on 5.3 branch. I want to ask the community if anyone has 
any objections on just keeping master as the working branch and have branches 
when they are needed (say documentation, feature work
etc) and once they are merged they can be removed. We have git tags to identify 
past release so is it also alright with everyone to remove the support branches 
such as 5.3/5.2 etc.

This way we will have:
- one main working branch (master)
- branch based workflow: feature branches for doing feature work, pull requests 
or reviewboard for bugfixes for non-committers
- master is aimed to remain stable
- master will have its own TravisCI and tests (in upcoming weeks)
- CloudMonkey aims for progressive/rolling releases that are backward 
compatible with older releases and have clean upgrades

For this please vote with your comments/suggestions;

+1  approve
+0  no opinion
-1  disapprove (and reason why)

Regards,
Rohit Yadav
Software Architect, ShapeBlue
M. +91 8826230892 | rohit.ya...@shapeblue.com
Blog: bhaisaab.org | Twitter: @_bhaisaab PS. If you see any footer below, I did 
not add it :) Find out more about ShapeBlue and our range of CloudStack related 
services

IaaS Cloud Design & Build<http://shapeblue.com/iaas-cloud-design-and-build//
>
CSForge – rapid IaaS deployment framework<http://shapeblue.com/csforge/>
CloudStack Consulting<http://shapeblue.com/cloudstack-consultancy/>
CloudStack Software Engineering<http://shapeblue.com/cloudstack-software-
engineering/>
CloudStack Infrastructure Support<http://shapeblue.com/ 
cloudstack-infrastructure-support/>
CloudStack Bootcamp Training Courses<http://shapeblue.com/ cloudstack-training/>

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.



--
Sent from Windows Phone

Re: [VOTE] Simplify CloudMonkey's branching/maintenance process

2014-12-10 Thread Erik Weber 
On tir. 9. des. 2014 at 14.27 Rohit Yadav  wrote:

> Hi,
>
> CloudMonkey's git repo history is mostly linear and the work on master
> is simply getting synced on 5.3 branch. I want to ask the community if
> anyone has any objections on just keeping master as the working branch
> and have branches when they are needed (say documentation, feature work
> etc) and once they are merged they can be removed. We have git tags to
> identify past release so is it also alright with everyone to remove the
> support branches such as 5.3/5.2 etc.
>
> This way we will have:
> - one main working branch (master)
> - branch based workflow: feature branches for doing feature work, pull
> requests or reviewboard for bugfixes for non-committers
> - master is aimed to remain stable
> - master will have its own TravisCI and tests (in upcoming weeks)
> - CloudMonkey aims for progressive/rolling releases that are backward
> compatible with older releases and have clean upgrades
>
> For this please vote with your comments/suggestions;
>
> +1  approve
> +0  no opinion
> -1  disapprove (and reason why)
>
>

+1, seems like the best thing to do.

-- 
Erik

Re: [VOTE] Simplify CloudMonkey's branching/maintenance process

2014-12-09 Thread Abhinandan Prateek 
+1, keep it simple


> On 10-Dec-2014, at 4:21 am, Daan Hoogland  wrote:
>
> +1 , I wish we could make such a call on the stack.
>
> On Tue, Dec 9, 2014 at 7:14 PM, sebgoa  wrote:
>>
>> On Dec 9, 2014, at 2:25 PM, Rohit Yadav  wrote:
>>
>>> Hi,
>>>
>>> CloudMonkey's git repo history is mostly linear and the work on master
>>> is simply getting synced on 5.3 branch. I want to ask the community if
>>> anyone has any objections on just keeping master as the working branch
>>> and have branches when they are needed (say documentation, feature work
>>> etc) and once they are merged they can be removed. We have git tags to
>>> identify past release so is it also alright with everyone to remove the
>>> support branches such as 5.3/5.2 etc.
>>>
>>> This way we will have:
>>> - one main working branch (master)
>>> - branch based workflow: feature branches for doing feature work, pull
>>> requests or reviewboard for bugfixes for non-committers
>>> - master is aimed to remain stable
>>> - master will have its own TravisCI and tests (in upcoming weeks)
>>> - CloudMonkey aims for progressive/rolling releases that are backward
>>> compatible with older releases and have clean upgrades
>>>
>>> For this please vote with your comments/suggestions;
>>>
>>> +1  approve
>>> +0  no opinion
>>> -1  disapprove (and reason why)
>>>
>>
>> +1
>>
>> that's what we do in libcloud.
>>
>> You could have a situation where you want to release a minor, and have to 
>> build it in a release branch. Cherry picking from master.
>>
>> But the next major already will have all the cherry picks from the previous 
>> minor.
>>
>> so +1 for linear and rolling upgrade.
>>
>>
>>> Regards,
>>> Rohit Yadav
>>> Software Architect, ShapeBlue
>>> M. +91 8826230892 | rohit.ya...@shapeblue.com
>>> Blog: bhaisaab.org | Twitter: @_bhaisaab
>>> PS. If you see any footer below, I did not add it :)
>>> Find out more about ShapeBlue and our range of CloudStack related services
>>>
>>> IaaS Cloud Design & 
>>> Build
>>> CSForge – rapid IaaS deployment framework
>>> CloudStack Consulting
>>> CloudStack Software 
>>> Engineering
>>> 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.
>>
>
>
>
> --
> Daan

Find out more about ShapeBlue and our range of CloudStack related services

IaaS Cloud Design & Build
CSForge – rapid IaaS deployment framework
CloudStack Consulting
CloudStack Software 
Engineering
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 licens

Re: [VOTE] Simplify CloudMonkey's branching/maintenance process

2014-12-09 Thread Mike Tutkowski 
+1

On Tuesday, December 9, 2014, Rajani Karuturi  wrote:

> +1
>
>
> On Tue, Dec 9, 2014 at 18:55 PM, Rohit Yadav  >
> wrote:
>
> Hi,
>
> CloudMonkey's git repo history is mostly linear and the work on master
> is simply getting synced on 5.3 branch. I want to ask the community if
> anyone has any objections on just keeping master as the working branch
> and have branches when they are needed (say documentation, feature work
> etc) and once they are merged they can be removed. We have git tags to
> identify past release so is it also alright with everyone to remove the
> support branches such as 5.3/5.2 etc.
>
> This way we will have:
> - one main working branch (master)
> - branch based workflow: feature branches for doing feature work, pull
> requests or reviewboard for bugfixes for non-committers
> - master is aimed to remain stable
> - master will have its own TravisCI and tests (in upcoming weeks)
> - CloudMonkey aims for progressive/rolling releases that are backward
> compatible with older releases and have clean upgrades
>
> For this please vote with your comments/suggestions;
>
> +1  approve
> +0  no opinion
> -1  disapprove (and reason why)
>
> Regards,
> Rohit Yadav
> Software Architect, ShapeBlue
> M. +91 8826230892 | rohit.ya...@shapeblue.com 
> Blog: bhaisaab.org | Twitter: @_bhaisaab
> PS. If you see any footer below, I did not add it :)
> Find out more about ShapeBlue and our range of CloudStack related services
>
> IaaS Cloud Design & Build<
> http://shapeblue.com/iaas-cloud-design-and-build//
> >
> CSForge – rapid IaaS deployment framework
> CloudStack Consulting
> CloudStack Software Engineering engineering/>
> CloudStack Infrastructure Support cloudstack-infrastructure-support/>
> CloudStack Bootcamp Training Courses cloudstack-training/>
>
> 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.
>
>
>
> --
> Sent from Windows Phone
>


-- 
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkow...@solidfire.com
o: 303.746.7302
Advancing the way the world uses the cloud
*™*

Re: [VOTE] Simplify CloudMonkey's branching/maintenance process

2014-12-09 Thread Rajani Karuturi 
+1


On Tue, Dec 9, 2014 at 18:55 PM, Rohit Yadav 
wrote:

Hi,

CloudMonkey's git repo history is mostly linear and the work on master
is simply getting synced on 5.3 branch. I want to ask the community if
anyone has any objections on just keeping master as the working branch
and have branches when they are needed (say documentation, feature work
etc) and once they are merged they can be removed. We have git tags to
identify past release so is it also alright with everyone to remove the
support branches such as 5.3/5.2 etc.

This way we will have:
- one main working branch (master)
- branch based workflow: feature branches for doing feature work, pull
requests or reviewboard for bugfixes for non-committers
- master is aimed to remain stable
- master will have its own TravisCI and tests (in upcoming weeks)
- CloudMonkey aims for progressive/rolling releases that are backward
compatible with older releases and have clean upgrades

For this please vote with your comments/suggestions;

+1  approve
+0  no opinion
-1  disapprove (and reason why)

Regards,
Rohit Yadav
Software Architect, ShapeBlue
M. +91 8826230892 | rohit.ya...@shapeblue.com
Blog: bhaisaab.org | Twitter: @_bhaisaab
PS. If you see any footer below, I did not add it :)
Find out more about ShapeBlue and our range of CloudStack related services

IaaS Cloud Design & Build
CSForge – rapid IaaS deployment framework
CloudStack Consulting
CloudStack Software Engineering
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.



-- 
Sent from Windows Phone

Re: [VOTE] Simplify CloudMonkey's branching/maintenance process

2014-12-09 Thread Ian Duffy 
+1, it makes sense for cloudmonkey :)

On 9 December 2014 at 22:51, Daan Hoogland  wrote:

> +1 , I wish we could make such a call on the stack.
>
> On Tue, Dec 9, 2014 at 7:14 PM, sebgoa  wrote:
> >
> > On Dec 9, 2014, at 2:25 PM, Rohit Yadav 
> wrote:
> >
> >> Hi,
> >>
> >> CloudMonkey's git repo history is mostly linear and the work on master
> >> is simply getting synced on 5.3 branch. I want to ask the community if
> >> anyone has any objections on just keeping master as the working branch
> >> and have branches when they are needed (say documentation, feature work
> >> etc) and once they are merged they can be removed. We have git tags to
> >> identify past release so is it also alright with everyone to remove the
> >> support branches such as 5.3/5.2 etc.
> >>
> >> This way we will have:
> >> - one main working branch (master)
> >> - branch based workflow: feature branches for doing feature work, pull
> >> requests or reviewboard for bugfixes for non-committers
> >> - master is aimed to remain stable
> >> - master will have its own TravisCI and tests (in upcoming weeks)
> >> - CloudMonkey aims for progressive/rolling releases that are backward
> >> compatible with older releases and have clean upgrades
> >>
> >> For this please vote with your comments/suggestions;
> >>
> >> +1  approve
> >> +0  no opinion
> >> -1  disapprove (and reason why)
> >>
> >
> > +1
> >
> > that's what we do in libcloud.
> >
> > You could have a situation where you want to release a minor, and have
> to build it in a release branch. Cherry picking from master.
> >
> > But the next major already will have all the cherry picks from the
> previous minor.
> >
> > so +1 for linear and rolling upgrade.
> >
> >
> >> Regards,
> >> Rohit Yadav
> >> Software Architect, ShapeBlue
> >> M. +91 8826230892 | rohit.ya...@shapeblue.com
> >> Blog: bhaisaab.org | Twitter: @_bhaisaab
> >> PS. If you see any footer below, I did not add it :)
> >> Find out more about ShapeBlue and our range of CloudStack related
> services
> >>
> >> IaaS Cloud Design & Build<
> http://shapeblue.com/iaas-cloud-design-and-build//>
> >> CSForge – rapid IaaS deployment framework >
> >> CloudStack Consulting
> >> CloudStack Software Engineering<
> http://shapeblue.com/cloudstack-software-engineering/>
> >> CloudStack Infrastructure Support<
> http://shapeblue.com/cloudstack-infrastructure-support/>
> >> CloudStack Bootcamp Training Courses<
> http://shapeblue.com/cloudstack-training/>
> >>
> >> 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.
> >
>
>
>
> --
> Daan
>

Re: [VOTE] Simplify CloudMonkey's branching/maintenance process

2014-12-09 Thread Daan Hoogland 
+1 , I wish we could make such a call on the stack.

On Tue, Dec 9, 2014 at 7:14 PM, sebgoa  wrote:
>
> On Dec 9, 2014, at 2:25 PM, Rohit Yadav  wrote:
>
>> Hi,
>>
>> CloudMonkey's git repo history is mostly linear and the work on master
>> is simply getting synced on 5.3 branch. I want to ask the community if
>> anyone has any objections on just keeping master as the working branch
>> and have branches when they are needed (say documentation, feature work
>> etc) and once they are merged they can be removed. We have git tags to
>> identify past release so is it also alright with everyone to remove the
>> support branches such as 5.3/5.2 etc.
>>
>> This way we will have:
>> - one main working branch (master)
>> - branch based workflow: feature branches for doing feature work, pull
>> requests or reviewboard for bugfixes for non-committers
>> - master is aimed to remain stable
>> - master will have its own TravisCI and tests (in upcoming weeks)
>> - CloudMonkey aims for progressive/rolling releases that are backward
>> compatible with older releases and have clean upgrades
>>
>> For this please vote with your comments/suggestions;
>>
>> +1  approve
>> +0  no opinion
>> -1  disapprove (and reason why)
>>
>
> +1
>
> that's what we do in libcloud.
>
> You could have a situation where you want to release a minor, and have to 
> build it in a release branch. Cherry picking from master.
>
> But the next major already will have all the cherry picks from the previous 
> minor.
>
> so +1 for linear and rolling upgrade.
>
>
>> Regards,
>> Rohit Yadav
>> Software Architect, ShapeBlue
>> M. +91 8826230892 | rohit.ya...@shapeblue.com
>> Blog: bhaisaab.org | Twitter: @_bhaisaab
>> PS. If you see any footer below, I did not add it :)
>> Find out more about ShapeBlue and our range of CloudStack related services
>>
>> IaaS Cloud Design & Build
>> CSForge – rapid IaaS deployment framework
>> CloudStack Consulting
>> CloudStack Software 
>> Engineering
>> 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.
>



-- 
Daan

Re: [VOTE] Simplify CloudMonkey's branching/maintenance process

2014-12-09 Thread sebgoa 

On Dec 9, 2014, at 2:25 PM, Rohit Yadav  wrote:

> Hi,
> 
> CloudMonkey's git repo history is mostly linear and the work on master
> is simply getting synced on 5.3 branch. I want to ask the community if
> anyone has any objections on just keeping master as the working branch
> and have branches when they are needed (say documentation, feature work
> etc) and once they are merged they can be removed. We have git tags to
> identify past release so is it also alright with everyone to remove the
> support branches such as 5.3/5.2 etc.
> 
> This way we will have:
> - one main working branch (master)
> - branch based workflow: feature branches for doing feature work, pull
> requests or reviewboard for bugfixes for non-committers
> - master is aimed to remain stable
> - master will have its own TravisCI and tests (in upcoming weeks)
> - CloudMonkey aims for progressive/rolling releases that are backward
> compatible with older releases and have clean upgrades
> 
> For this please vote with your comments/suggestions;
> 
> +1  approve
> +0  no opinion
> -1  disapprove (and reason why)
> 

+1

that's what we do in libcloud.

You could have a situation where you want to release a minor, and have to build 
it in a release branch. Cherry picking from master.

But the next major already will have all the cherry picks from the previous 
minor.

so +1 for linear and rolling upgrade. 


> Regards,
> Rohit Yadav
> Software Architect, ShapeBlue
> M. +91 8826230892 | rohit.ya...@shapeblue.com
> Blog: bhaisaab.org | Twitter: @_bhaisaab
> PS. If you see any footer below, I did not add it :)
> Find out more about ShapeBlue and our range of CloudStack related services
> 
> IaaS Cloud Design & Build
> CSForge – rapid IaaS deployment framework
> CloudStack Consulting
> CloudStack Software 
> Engineering
> 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.

RE: [VOTE] Simplify CloudMonkey's branching/maintenance process

2014-12-09 Thread Stephen Turner 
+1 as long as CloudMonkey remains backwards compatible with older CloudStack 
releases, so that we don't have to preserve old monkeys to talk to old stacks.

-- 
Stephen Turner


-Original Message-
From: Rohit Yadav [mailto:rohit.ya...@shapeblue.com] 
Sent: 09 December 2014 13:26
To: dev
Subject: [VOTE] Simplify CloudMonkey's branching/maintenance process

Hi,

CloudMonkey's git repo history is mostly linear and the work on master is 
simply getting synced on 5.3 branch. I want to ask the community if anyone has 
any objections on just keeping master as the working branch and have branches 
when they are needed (say documentation, feature work
etc) and once they are merged they can be removed. We have git tags to identify 
past release so is it also alright with everyone to remove the support branches 
such as 5.3/5.2 etc.

This way we will have:
- one main working branch (master)
- branch based workflow: feature branches for doing feature work, pull requests 
or reviewboard for bugfixes for non-committers
- master is aimed to remain stable
- master will have its own TravisCI and tests (in upcoming weeks)
- CloudMonkey aims for progressive/rolling releases that are backward 
compatible with older releases and have clean upgrades

For this please vote with your comments/suggestions;

+1  approve
+0  no opinion
-1  disapprove (and reason why)

Regards,
Rohit Yadav
Software Architect, ShapeBlue
M. +91 8826230892 | rohit.ya...@shapeblue.com
Blog: bhaisaab.org | Twitter: @_bhaisaab PS. If you see any footer below, I did 
not add it :) Find out more about ShapeBlue and our range of CloudStack related 
services

IaaS Cloud Design & Build<http://shapeblue.com/iaas-cloud-design-and-build//>
CSForge – rapid IaaS deployment framework<http://shapeblue.com/csforge/>
CloudStack Consulting<http://shapeblue.com/cloudstack-consultancy/>
CloudStack Software 
Engineering<http://shapeblue.com/cloudstack-software-engineering/>
CloudStack Infrastructure 
Support<http://shapeblue.com/cloudstack-infrastructure-support/>
CloudStack Bootcamp Training Courses<http://shapeblue.com/cloudstack-training/>

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.

Re: [VOTE] Simplify CloudMonkey's branching/maintenance process

2014-12-09 Thread Wido den Hollander 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1



On 12/09/2014 02:25 PM, Rohit Yadav wrote:
> Hi,
> 
> CloudMonkey's git repo history is mostly linear and the work on
> master is simply getting synced on 5.3 branch. I want to ask the
> community if anyone has any objections on just keeping master as
> the working branch and have branches when they are needed (say
> documentation, feature work etc) and once they are merged they can
> be removed. We have git tags to identify past release so is it also
> alright with everyone to remove the support branches such as
> 5.3/5.2 etc.
> 
> This way we will have: - one main working branch (master) - branch
> based workflow: feature branches for doing feature work, pull 
> requests or reviewboard for bugfixes for non-committers - master is
> aimed to remain stable - master will have its own TravisCI and
> tests (in upcoming weeks) - CloudMonkey aims for
> progressive/rolling releases that are backward compatible with
> older releases and have clean upgrades
> 
> For this please vote with your comments/suggestions;
> 

+1

I think CloudMonkey is not complex enough (that's a good thing!) to
justify the need for multiple branches.

Just tags on master should be sufficient I think.

Wido

> +1  approve +0  no opinion -1  disapprove (and reason why)
> 
> Regards, Rohit Yadav Software Architect, ShapeBlue M. +91
> 8826230892 | rohit.ya...@shapeblue.com Blog: bhaisaab.org |
> Twitter: @_bhaisaab PS. If you see any footer below, I did not add
> it :) Find out more about ShapeBlue and our range of CloudStack
> related services
> 
> IaaS Cloud Design & 
> Build CSForge –
> rapid IaaS deployment framework 
> CloudStack
> Consulting CloudStack
> Software 
> Engineering 
> 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.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJUhzfwAAoJEAGbWC3bPspCIGkQAJB5BEdY8ggEUNknOt0k0aMH
u+bq008ox5T3HOm9sdeeGS3oOJkPTH3Recwa7SKNnd1m0sS0D039YaQT0GUuOBxc
QOPVJelR+blRzQO9x4nyI9wT2rftnKyR5GuQhwHg5Z73v9mqj1U8RIKu44rnRDOj
kSlvR25sCxqgec1YKvQwi43bs9H/VBt+i9OnSVMjBFGRaGquM2jTE5SAQr5pG3NA
tAodLFYTEtbDeAOtOJ/Cn9hnME62exacyuhatZsbC2zpaQcc2Z7mLwyzjaVrDibl
BMZNVBONiA7HKRvQ7oqXPru4x0vQD+4nmlLxTd4wGzAgfqIVEBd1OxWGa2QnDWir
b+iS2uq9XrWwo7ijwcxZwOG1GBSUlGUWETKM3GHcv5LHmtExIyR0ojcT9sc0UiYr
zig8kgsSjj7q2K/5TtepNqdtmbOH2ni+3tQAADAvFhDEOxIa1cx3Lb4aXQRUCpbQ
PiIlVi9Ry2hfYsJEBce+XdtAiD8IERYbnMSLfKDVlvny8Ce+5AozKaccF2rAa5iv
B9qgYEJtPXoLC15KEkPd+t9WV7UPLxvCQxDic3UHSC1Fx6I6E/xCscgCPp5e2Vk0
A3iMKgQLXbFcV/iYlzF2GpYgKowEH1P3K7F+YfyG785sdCHqzCPvq2T/0biCt+Ye
EZGhYpyV0fetC0QTD3ZW
=gzBp
-END PGP SIGNATURE-

[VOTE] Simplify CloudMonkey's branching/maintenance process

2014-12-09 Thread Rohit Yadav 

Hi,

CloudMonkey's git repo history is mostly linear and the work on master
is simply getting synced on 5.3 branch. I want to ask the community if
anyone has any objections on just keeping master as the working branch
and have branches when they are needed (say documentation, feature work
etc) and once they are merged they can be removed. We have git tags to
identify past release so is it also alright with everyone to remove the
support branches such as 5.3/5.2 etc.

This way we will have:
- one main working branch (master)
- branch based workflow: feature branches for doing feature work, pull
requests or reviewboard for bugfixes for non-committers
- master is aimed to remain stable
- master will have its own TravisCI and tests (in upcoming weeks)
- CloudMonkey aims for progressive/rolling releases that are backward
compatible with older releases and have clean upgrades

For this please vote with your comments/suggestions;

+1  approve
+0  no opinion
-1  disapprove (and reason why)

Regards,
Rohit Yadav
Software Architect, ShapeBlue
M. +91 8826230892 | rohit.ya...@shapeblue.com
Blog: bhaisaab.org | Twitter: @_bhaisaab
PS. If you see any footer below, I did not add it :)
Find out more about ShapeBlue and our range of CloudStack related services

IaaS Cloud Design & Build
CSForge – rapid IaaS deployment framework
CloudStack Consulting
CloudStack Software 
Engineering
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.