Re: [racket-dev] Release process for split repos

[Vincent St-Amour]

That sounds good to me.

One concern, though: it looks like recreating old releases requires that
all the participating repos (1) still exist, (2) have the same
name/location, and (3) still have the release tags. I'm not too worried
about (1) and (3), but I could see (2) happening if, e.g., a package
changes maintainer (and therefore location), or if we have to move away
from github at some point.

IIUC, archiving snapshots of the participating repos when the release is
finalized may solve that problem. Does that sound reasonable?

Vincent



At Fri, 23 Jan 2015 15:31:21 -0500,
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

_
  Racket Developers list:
  http://lists.racket-lang.org/dev

Re: [racket-dev] Release process for split repos

[Neil Toronto]

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


_
 Racket Developers list:
 http://lists.racket-lang.org/dev