Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can we cut a v2.8.1 release, please? (Also: GPG key expired) #1127

Closed
srenatus opened this issue Nov 14, 2017 · 3 comments
Closed

Can we cut a v2.8.1 release, please? (Also: GPG key expired) #1127

srenatus opened this issue Nov 14, 2017 · 3 comments

Comments

@srenatus
Copy link
Contributor

The 10 commits to master since v2.8.0 look OK to me. I'm obviously interested in #1116 and #1123, but cherry-picking those doesn't seem to make too much sense given that the commits since 2.8.0 are mostly these.

Also, GitHub shows the key used to sign the v2.8.0 tag, A05E509132EF40C5, has expired:

screen shot 2017-11-14 at 08 22 18

@ericchiang I think this is you 😉

Thanks! 😃

@srenatus srenatus changed the title Can we cut a v2.8.1 release? (Also: GPG key expired) Can we cut a v2.8.1 release, please? (Also: GPG key expired) Nov 15, 2017
@ericchiang
Copy link
Contributor

Thanks. I've modified the expiry of my public key. Green checkboxes should be back.

I'll cherry pick #1116 and #1123 and do a v2.8.1.

@ericchiang
Copy link
Contributor

@srenatus
Copy link
Contributor Author

@ericchiang thanks a lot!

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

No branches or pull requests

2 participants