i'm on the master branch reset to the head of 1.9....
# announcea
aloof-angle-91616
08/30/2018, 11:30 PMi'm on the master branch reset to the head of 1.9.x
w
witty-crayon-22786
08/31/2018, 12:19 AMshould release from the appropriate point in that branch
a
aloof-angle-91616
08/31/2018, 12:19 AMthe docs say otherwise
aloof-angle-91616
08/31/2018, 12:20 AMw
witty-crayon-22786
08/31/2018, 12:20 AMi'll fix that.
a
aloof-angle-91616
08/31/2018, 12:20 AMFirst, ensure you are on the master branch at the release commit. If new commits have landed after your release commit, you can reset to your commit (git reset --hard <sha>).
aloof-angle-91616
08/31/2018, 12:20 AMok
aloof-angle-91616
08/31/2018, 12:20 AMyou'll also want to fix the section above on dry runs
aloof-angle-91616
08/31/2018, 12:20 AM"if so, releases should only be published from master, so get on master and ensure your version number commit is present"
w
witty-crayon-22786
08/31/2018, 12:21 AMwill fix.
a
aloof-angle-91616
08/31/2018, 12:21 AMthanks!
w
witty-crayon-22786
08/31/2018, 12:21 AMyou should release from the release branch, with the version bump
a
aloof-angle-91616
08/31/2018, 12:21 AMgot it
aloof-angle-91616
08/31/2018, 12:21 AMdoing that now
aloof-angle-91616
08/31/2018, 12:21 AMfrom
097254cb219cb8066604375d44f4889bc9700636aloof-angle-91616
08/31/2018, 12:22 AMand 1.9.x checked out
aloof-angle-91616
08/31/2018, 12:22 AMeverything as you said
w
witty-crayon-22786
08/31/2018, 12:22 AMyep, looks good.
a
aloof-angle-91616
08/31/2018, 12:36 AM(i didn't do it yet -- making sure i'm using the same gpg key i did last time)
aloof-angle-91616
08/31/2018, 12:37 AM(not a problem)
aloof-angle-91616
08/31/2018, 12:42 AMrunning it now