[L2Ork-dev] request for mentorship: build infrastructure

[Albert Graef]

On Fri, Mar 17, 2017 at 2:13 AM, Jonathan Wilkes <jancsika at yahoo.com> wrote:

> The tags should be pretty easy.  I'll start with those when I get a chance.
>

I can also take care of it, but it's really not a big deal. The commands,
say, for the upcoming 2.1.2 would be:

    git tag 2.1.2
    git push origin 2.1.2

The first one creates a tag pointing to the current commit, the second one
pushes the tag to the server (just a `git push` doesn't do that). If you
forgot to tag a release, you can also do that retroactively, by just giving
the commit hash:

    git tag 2.0 a243cb31314248c2f39996138e7fd60b429e9fe5
    git push origin 2.0

If you made a mistake, the commands to forcibly move an existing tag to the
current commit (again, you can just add the md5 hash if you want to move
the tag to a given commit instead) and then force-push it are the following
(use with care):

    git tag -f 2.1.2
    git push -f origin 2.1.2

In any case, I can then just pull your tags over to the github mirror and,
once the binaries are out, add the release notes and upload the binaries on
github, in the same fashion as I already did for the 2.1.1 release.

So your workflow doesn't have to change at all, except that you add the
tags to the appropriate commits when you're baking a new release.


> I can probably just re-run the ci for the missing 2.0 binaries.  That will
> at least
> get me Linux and OSX 10.11 binaries.
>

Not really that important, now that 2.1.1 is already out. I just thought
I'd ask in case you still have these lying around somewhere. (The OSX 10.11
and Windows 32 bit binaries for 2.0 I still had on my hard disk, so these
are already available through the github mirror.)

Albert

-- 
Dr. Albert Gr"af
Computer Music Research Group, JGU Mainz, Germany
Email:  aggraef at gmail.com
WWW:    https://plus.google.com/+AlbertGraef
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://disis.music.vt.edu/pipermail/l2ork-dev/attachments/20170317/a40977cf/attachment-0001.html>