[racket-dev] Release process for split repos

I like the general idea. I especially like that you've included 
instructions for repo managers like me who will likely forget everything 
about git branch management and cherry picking between releases.

In the past, you've played the part of central reviewer for requests to 
merge to the release branch. Are we going to try for the same kind of 
consistency now, or leave it up to repo managers?

Neil ⊥

On 01/23/2015 03:31 PM, Ryan Culpepper wrote:
> I’ve added a draft of a new release process that takes the repository split into account. The main difference is that there is no longer a single release branch under central management; instead, there is a release branch for each repository, and management responsibilities for package release branches is distributed.
>
> The wiki page is here:
>
>    https://github.com/plt/racket/wiki/Release-process
>
> Please review, ask questions, and point out ambiguities and potential problems.
>
> Ryan
>
>
> _________________________
>    Racket Developers list:
>    http://lists.racket-lang.org/dev