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

clarify operating systems with available binaries #256

Merged
merged 3 commits into from Sep 18, 2019

Conversation

ayazhafiz
Copy link
Contributor

This is very much a nit. Feel free to close and discard this PR if you wish.

It may also be worth getting rid of this line entirely. It appears that since 0.3.12 there have
only been Windows binary releases (excluding one linux one in 0.3.13).

This is very much a nit. Feel free to close and discard this PR if you wish.

It may also be worth getting rid of this line entirely. It appears that since 0.3.12 there have
only been Windows binary releases (excluding one linux one in 0.3.13).
@RalfJung
Copy link
Collaborator

For 0.3.16, we seem to only have source releases on GH -- but when doing a release, I am just pushing a tag; then @japaric is doing "something" to add artifacts on GitHub (I don't even know how that works).

So probably it would make most sense to just remove the remark about binary releases, and point everyone at crates.io. Could you do that?

@ayazhafiz
Copy link
Contributor Author

ayazhafiz commented Sep 15, 2019

Yep! I removed the remark entirely. Let me know id you'd rather link the crates.io page.

README.md Outdated Show resolved Hide resolved
@RalfJung
Copy link
Collaborator

Thanks!

bors r+

bors bot added a commit that referenced this pull request Sep 16, 2019
256: clarify operating systems with available binaries r=RalfJung a=ayazhafiz

This is very much a nit. Feel free to close and discard this PR if you wish.

It may also be worth getting rid of this line entirely. It appears that since 0.3.12 there have
only been Windows binary releases (excluding one linux one in 0.3.13).

Co-authored-by: hafiz <ayaz.hafiz.1@gmail.com>
Co-authored-by: ayazhafiz <ayaz.hafiz.1@gmail.com>
@bors
Copy link
Contributor

bors bot commented Sep 16, 2019

Build failed

@RalfJung
Copy link
Collaborator

Ah, this is blocked on getting rust-lang/rust#64444 landed.

@RalfJung
Copy link
Collaborator

bors retry

bors bot added a commit that referenced this pull request Sep 17, 2019
256: clarify operating systems with available binaries r=RalfJung a=ayazhafiz

This is very much a nit. Feel free to close and discard this PR if you wish.

It may also be worth getting rid of this line entirely. It appears that since 0.3.12 there have
only been Windows binary releases (excluding one linux one in 0.3.13).

Co-authored-by: hafiz <ayaz.hafiz.1@gmail.com>
Co-authored-by: ayazhafiz <ayaz.hafiz.1@gmail.com>
@bors
Copy link
Contributor

bors bot commented Sep 17, 2019

Build failed

@RalfJung
Copy link
Collaborator

bors retry

bors bot added a commit that referenced this pull request Sep 18, 2019
256: clarify operating systems with available binaries r=RalfJung a=ayazhafiz

This is very much a nit. Feel free to close and discard this PR if you wish.

It may also be worth getting rid of this line entirely. It appears that since 0.3.12 there have
only been Windows binary releases (excluding one linux one in 0.3.13).

Co-authored-by: hafiz <ayaz.hafiz.1@gmail.com>
Co-authored-by: ayazhafiz <ayaz.hafiz.1@gmail.com>
@bors
Copy link
Contributor

bors bot commented Sep 18, 2019

Build succeeded

@bors bors bot merged commit 8c8f54c into japaric:master Sep 18, 2019
@jethrogb
Copy link
Collaborator

then @japaric is doing "something" to add artifacts on GitHub (I don't even know how that works).

Oh, huh, I thought this was automatic through CI, but it seems this didn't happen for 0.3.16...

@RalfJung
Copy link
Collaborator

I see no indication in our CI that it would do anything like that. But I honestly don't know. I don't even know what it takes to turn a git tag into a GH "release"... not all tags seem to be treated as releases. Whatever.^^

@jethrogb
Copy link
Collaborator

jethrogb commented Sep 18, 2019

I was assuming this has something to do with it. If not, I don't understand what the deploy part does.

@RalfJung
Copy link
Collaborator

Hm, yeah. No idea what that part does. And I hope that's not a secret API key we have in that file...

@ayazhafiz ayazhafiz deleted the readme/os branch September 18, 2019 13:48
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.

None yet

3 participants