Re: [ANNOUNCE] New PMC Member: Rajani Karuturi

[Ian Duffy]

Congrats Rajani! :)

On 17 October 2014 16:47, Mike Tutkowski 
wrote:

> Congratulations!
>
> On Friday, October 17, 2014, Daan Hoogland 
> wrote:
>
> > The Project Management Committee (PMC) for Apache CloudStack are pleased
> to
> > announce that Rajani Karuturi has accepted our invitation to join the
> PMC.
> >
> > Please join me in congratulating her.
> >
> > On behalf of the Apache CloudStack PMC
> > --
> > Daan
> >
>
>
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkow...@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the cloud
> *™*
>

[PROPOSAL] Move to github PR only during moratorium on commit

[sebgoa]

After [1] I would like to officially bring up the following proposal.

[Proposal]

All commits come through github PR, *even* for committers. We declare a 
moratorium period (agreed suspension of activity) during which direct commit to 
master is forbidden.
Only the master RM is allowed to merge PR in master (we define a master RM). If 
direct commit to master is done, master RM reverts without warning. Same for 
4.5 and 4.4. branches.


This is drastic and I am sure some folks will not like it, but here is my 
justification for such a measure:

[Reasons]:

Our commit and release processes have so far been based on the idea that 
development happens on master and that a release branch is cut from master 
(unstable development branch). Then a different set of community members harden 
the release branch, QA and bring it to GA level. During that time development 
keeps on going in master.

This is an OK process if we have the luxury of having a QA team and can cope 
with split personality of being developers and release managers. 

My point of view is that as a community we cannot afford such a split brain 
organization and our experience overt the last year proves my point (delayed 
release date, broken builds, features merged without warning…)

We can avoid this by cutting a release branch from a stable one (from the 
start), then as you (Daan) have mentioned several times, fix bugs in the 
release branch and merge them back in the stable source of the release (be it 
master). 

Feature development need to be done outside master, period. Not only for 
non-committers but also for committers. And merge request need to be called. 
This will help review and avoid surprises.

New git workflow were proposed and shutdown, mostly calling for better CI to 
solve quality issues. CI will not solve our quality issues alone. We need to 
better police ourselves.

To avoid long discussions, I propose this simple but drastic measure. We move 
all our commits to github PR until 4.5 is out, this stands for committers and 
non-committers, direct commits (especially to master) would be reverted 
immediately.


Our development and release process is broken, we cannot continue like this, 
let's fix it.

[1] http://markmail.org/thread/xeliefp3oleq3g54

-sebastien

Re: [PROPOSAL] Move to github PR only during moratorium on commit

[Rohit Yadav]

Hi,

> On 18-Oct-2014, at 2:30 pm, sebgoa  wrote:
>
> [Proposal]
> 
> All commits come through github PR, *even* for committers. We declare a 
> moratorium period (agreed suspension of activity) during which direct commit 
> to master is forbidden.
> Only the master RM is allowed to merge PR in master (we define a master RM). 
> If direct commit to master is done, master RM reverts without warning. Same 
> for 4.5 and 4.4. branches.
> 

+1

Much needed and Github is just more fun than RB any day. Merging gives us the 
benefit of reverting the merge by reverting on the merge commit which is useful 
to revert a merge that break some functionality and perhaps not the build.

Regards,
Rohit Yadav
Software Architect, ShapeBlue
M. +91 88 262 30892 | rohit.ya...@shapeblue.com
Blog: bhaisaab.org | 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.

test

[????????]

Re: test

[Daan Hoogland]

sorry for allowing this post, I clicked the accept instead of the reject
link.

On Sat, Oct 18, 2014 at 3:55 PM, 流年似水  wrote:

>


-- 
Daan