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

Upload feature list to s3 #25724

Closed
brson opened this Issue May 22, 2015 · 5 comments

Comments

Projects
None yet
4 participants
@brson
Copy link
Contributor

brson commented May 22, 2015

The feature list displayed during tidy is useful for reporting purposes. Have the doc build generate it so it's uploaded nightly, in json format probably.

@brson brson referenced this issue May 22, 2015

Closed

Automation metabug #17356

45 of 65 tasks complete
@brson

This comment has been minimized.

Copy link
Contributor Author

brson commented May 25, 2015

Let's upload it with the docs. Easiest.

The script src/etc/featureck.py knows how to extract metadata for all the features. Modify this script so that, if given a new command line argument, outputs that metadata in json format, then modify mk/docs.mk to call this script and output the json to the doc/ folder. That should be sufficient to upload the information.

@aturon json is sufficient right? You are going to further refine that data to put it on a website somewhere?

@aturon

This comment has been minimized.

Copy link
Member

aturon commented May 26, 2015

@brson json is great. The current intended use case is for a tool that generates stubs for the weekly subteam report stubs.

@steveklabnik

This comment has been minimized.

Copy link
Member

steveklabnik commented Nov 15, 2016

Triage: no change.

https://internals.rust-lang.org/t/the-most-used-unstable-features-in-rust/4370 is related and was posted recently.

@Mark-Simulacrum

This comment has been minimized.

Copy link
Member

Mark-Simulacrum commented May 16, 2017

No change once more. I'm somewhat uncertain that we want this, too; it feels like a nice thing I suppose but not all that useful. Unless I'm missing a use case of course.

@steveklabnik

This comment has been minimized.

Copy link
Member

steveklabnik commented Sep 24, 2018

Triage: we have the unstable book as a list of features, though that's not for exactly the same purpose. Regardless, nobody else has wanted this in the past few years, so I doubt it's ever going to be implemented. Closing!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.