[ckan-dev] Branching policy and standardizing on branch names

[James Gardner]

> Alternatively we could move towards a "continuous development" model
> where we have complete test coverage, fast automated test builds, easy
> deployment, feature flags and a "blame" functionality so that everyone
> can be confident and take responsibility for their own code.
>
> Pros and cons of both approaches.  The problem with dictator model is
> bottleneck, things waiting around to be merged, becoming harder to
> merge with time, etc etc.  The benefit is building in code reviews.

+1 to this. I'd like to see us move towards the continuous development 
model which is partly what all this packaging and server infrastructure 
talk is about.

James