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

Contributing guide should explain the issue tracker tags #25832

Merged
merged 1 commit into from
May 29, 2015
Merged

Contributing guide should explain the issue tracker tags #25832

merged 1 commit into from
May 29, 2015

Conversation

edunham
Copy link
Member

@edunham edunham commented May 27, 2015

I took a guess at what they mean, but could be totally wrong. Please comment, and I'll update the PR with corrections!

@rust-highfive
Copy link
Collaborator

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @pcwalton (or someone else) soon.

If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. The way Github handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.

Please see CONTRIBUTING.md for more information.


* Magenta, **B**-prefixed labels identify bugs which **belong** elsewhere.

* Green, **E**-prefixed labels flag **easy** or introductory bugs.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Here there's a few multiple levels within the E group itself, for example E-hard is a thing but E-easy definitely means easy. I'm... not sure what the E stands for!

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yeah, E- seems to categorize difficulty, but I'm not sure what a relevant mneumonic for that would be. Exigency status, perhaps? Or just "Easiness"?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suppose D may have been a better prefix... perhaps "experience"?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Experience?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, it's experience

labels to triage issues:

* Yellow, **A**-prefixed labels primarily relate to what part of the project
an issue is **about**.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The A is actually for the "area" of the project it's in.

@alexcrichton
Copy link
Member

Looks good to me! r=me with a squash

@brson
Copy link
Contributor

brson commented May 28, 2015

I'm about to delete A-an-interesting-project and rename I-regression to I-stable-regression.

A discussion at #25832 established what
the abbreviations mean.
@edunham
Copy link
Member Author

edunham commented May 28, 2015

Amended the squashed commit to remove mention of A-an-interesting-project. It never specifically discussed I-stable-regression. Thanks for the heads up that those are changing!

@alexcrichton
Copy link
Member

@bors: r+ 177531e

@alexcrichton
Copy link
Member

@bors: rollup

steveklabnik added a commit to steveklabnik/rust that referenced this pull request May 29, 2015
…lexcrichton

I took a guess at what they mean, but could be totally wrong. Please comment, and I'll update the PR with corrections!
steveklabnik added a commit to steveklabnik/rust that referenced this pull request May 29, 2015
…lexcrichton

I took a guess at what they mean, but could be totally wrong. Please comment, and I'll update the PR with corrections!
@bors
Copy link
Contributor

bors commented May 29, 2015

⌛ Testing commit 177531e with merge 42a59ae...

bors added a commit that referenced this pull request May 29, 2015
I took a guess at what they mean, but could be totally wrong. Please comment, and I'll update the PR with corrections!
@bors bors merged commit 177531e into rust-lang:master May 29, 2015
XMPPwocky pushed a commit to XMPPwocky/rust that referenced this pull request May 29, 2015
A discussion at rust-lang#25832 established what
the abbreviations mean.
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.

8 participants