How releases get made

I made the Koa master branches. In the interest of spreading the knowledge, here’s what I did:

First, I made a test branch called nedbat/test/k.1112b. A few repos had special branches pre-made to keep them on Elasticsearch 1.5. The tag_release tool can be told to override the reference for particular branches:

$ tag_release --doit --branch --skip-repo "*-internal" --override edx/cs_comments_service nedbat/for-koa --override edx/edx-notes-api nedbat/for-koa nedbat/test/k.1112b

I installed nedbat/test/k.1112b, and saw that it was successful. Time to make real master branches, at the same commits as nedbat/test/k.1112b.

$ tag_release --doit --branch --skip-repo "*-internal" --override-ref nedbat/test/k.1112b open-release/koa.master

After making two commits on the koa.master branch (to mark it as Koa and to create new Transifex projects), it’s time to create the open-release/koa.test01 branch:

$ tag_release --doit --branch --skip-invalid --search-branch open-release/koa.master --override-ref open-release/koa.master open-release/koa.test01

(Looking at these commands now, they have a mix of “skip-repo” and “skip-invalid” that doesn’t really have a reason.)

2 Likes