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