Sounds Great. Note, I think that we should all be free to manage our development environment however way we want, and so should not have to use coho (or any other opinionated tool).
However, in the interests of release automation, I think its very valuable to have a single consistent opinionated way we all organizing repos etc, so we can share scripts and code snippets that we expect to work for everyone. Looking at this list, I think coho is basically there (just needs some TLC), but I think fixing the issues with Windows Phone releases that Jesse brought up yesterday are top priority. -Michal On Wed, Mar 5, 2014 at 2:34 PM, Andrew Grieve <agri...@chromium.org> wrote: > Right now the repo contains a single script that has many sub-commands. > > I'd like to propose that the repo has the following mandate: > > 1. To hold release processes documentation > - e.g. StepsForToolsRelease > - e.g. CrowdIn documentation > > 2. To hold release automation scripts > - e.g. coho create-archive && coho verify-archive > - e.g. CrowdIn scripts > > 3. To hold committer process documentation > - e.g. ProcessingPullRequests > > 4. To hold generally useful dev scripts > - e.g. coho repo-clone > > > If this sounds good, then I'll stick it in the README.md >
