commits to master

[Cyrille Berger Skott]

On Tuesday 10 Apr 2012, Jaroslaw Staniek wrote:
> There are implications of such short release cycle however. I'd like
> to focus on just one today. Work on two or more versions can happen
> concurrently so it's important to have features easily moveable
> between releases since we're going to change plans (for many reasons).

I don't get that part. There is only one feature branch: master. All other 
"official" branches, futurestable or stable are closed for features.

The only time there could be a problem is if a terrible flaw is discovered in a 
feature, something that cannot be fixed in a timely fashion for a release. But 
frankly, that should be the exception (otherwise there is something terribely 
wrong with our workflow), and as such it can be manually removed from the 
automatically generated changelog.

-- 
Cyrille Berger Skott