Transitioning to the new Release Process

[Jesse Phillips]

On Wednesday, 9 January 2013 at 17:12:15 UTC, Jesse Phillips 
wrote:
> Before starting this I did come across Walter's complaint of 
> issues, but feel this needs a new thread. But didn't read all 
> replies.
>
> The new process introduces a new branch called staging. This is 
> _not_ used as one would first think.
>
> staging is created/updated _after_ release. This means a delay 
> in changes in master (breaking changes/new additions) and 
> release (a good thing). It also means that we have to do some 
> awkward delaying to get some useful changes into staging so 
> that it is different from this last release.

Since we don't have much opposition here for the staging process 
I will make my suggestion for this transition.

Since std.uni is up for review, lets plan that upon inclusion we 
move master into staging. This will be the next release as 
defined in our process. When another group of changes is 
considered ready we can make the release and update staging.

We could choose other changes, but I think this will be a good 
arbitrary point to make the transition (and not end up with an 
"empty" release).