Repository navigation
Bring existing compiler team repositories up-to-code. #65
Description
This issue originally only aimed to unify the labels across compiler team crates, but was generalized to list all of the things listed in the out-of-tree crates policy. The original description is below.
In order to perform triage in the weekly meeting across nominated issues in all compiler-team maintained repositories, we should make sure that there are a consistent set of labels that are used and that we update the triage meeting agenda to point to these searches.
Activity
davidtwco commentedon Apr 21, 2019
Having a quick look, I think these are the relevant repositories:
And these are the relevant labels that would need to be on each repo:
P-high,P-med,P-low,T-compilerandI-nominated. Not sure about these, might just be relevant for rust-lang/rust:regression-from-stable-to-beta,regression-from-stable-to-beta,beta-nominatedandstable-nominated.[-]Unify labels across compiler team repositories.[/-][+]Bring existing compiler team repositories up-to-code.[/+]davidtwco commentedon May 9, 2019
We want to make sure that all compiler team maintained repositories match the out-of-tree crates policy, that means making sure that the repositories on this list have the following:
Compilerteam with write,Assigneeswith read)READMEdescribing intended purpose of the crate, who maintains it and intended level of stability and maintenance.LICENSE-MITandLICENSE-APACHECODE_OF_CONDUCTP-high,P-med,P-low,T-compilerandI-nominated.@rust-highfive