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
Closed

Upload feature list to s3 #25724

brson opened this issue May 22, 2015 · 5 comments
Labels
C-enhancement Category: An issue proposing an enhancement or a PR with one. T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue.

Comments

@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 mentioned this issue May 22, 2015
65 tasks
@brson
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
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 steveklabnik added the C-enhancement Category: An issue proposing an enhancement or a PR with one. label May 26, 2015
@brson brson added the A-build label May 27, 2015
@steveklabnik
Copy link
Member

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
Copy link
Member

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.

@Mark-Simulacrum Mark-Simulacrum added the T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue. label Jun 22, 2017
@steveklabnik
Copy link
Member

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
Labels
C-enhancement Category: An issue proposing an enhancement or a PR with one. T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue.
Projects
None yet
Development

No branches or pull requests

4 participants