Skip to content

Conversation

@aykevl
Copy link
Member

@aykevl aykevl commented Jul 20, 2020

Perhaps some extra PRs need to be merged before actually merging this (and making the release) but I've already done some of the time consuming part here.

@niaow niaow added this to the v0.14 milestone Jul 20, 2020
@deadprogram
Copy link
Member

We should add the couple of PRs that made it into dev in the last couple of days to the changelog.

@aykevl
Copy link
Member Author

aykevl commented Aug 3, 2020

I have updated this PR to reflect the latest changes in the dev branch. I think this release is now ready.

@deadprogram
Copy link
Member

Incredible work from everyone on this release! Now merging.

@deadprogram deadprogram merged commit 154d4a7 into dev Aug 3, 2020
@deadprogram deadprogram deleted the release-v0.14.0 branch August 3, 2020 10:46
@deadprogram
Copy link
Member

deadprogram commented Aug 3, 2020

So I think to complete this release, we now need to do the following:

git checkout dev
git pull --rebase origin dev
git checkout master
git rebase dev
git branch -m master release
git push -u origin release

Once that is done, then we change the settings in the Github web interface to use release as the default branch *Settings > Branches > Default branch" and that should be it.

I have done this procedure already on GoCV repo for the most recent release there.

@aykevl
Copy link
Member Author

aykevl commented Aug 4, 2020

I have created the release branch and pushed it, but for some strange reason I can't push the master branch 🤔 but that shouldn't be a problem.
I have set the release branch as the default branch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants