Hi,
We've been losing bugs and stepping on one another's toes a bit
recently, so I spent last week doing bug triage and redid much of the
bug tagging. The results are not exactly wonderful, but if we ever
manage to squeeze github into supporting AND or NOT queries on tags (as
one might expect) it should be a vaguely-useful scheme. Meanwhile it at
least looks less like angry fruit salad, in terms of colour schemes.
I've documented the new tagging scheme over in the "issue tracking" part
of our development policy:
https://github.com/mozilla/rust/wiki/Note-development-policy
I've also written up the last round of "RFC policy" that we have been
pushing around inside the core developer group at mozilla lately. The
idea here is to minimize major changes that surprise people. So I've
written up what we agreed to at the end of the last meeting:
https://github.com/mozilla/rust/wiki/Note-RFC-process
Several people have been slinging around emails with "RFC" in the
subject line recently and/or tagging minor bugs as such. This policy
should clarify when to use that term a bit more.
Hopefully none of this affects anyone's workflow much beyond what one
would expect by shipping programs and starting to get users. Changes get
a bit more bureaucratic so there are fewer surprises. Film at 11.
Thanks for your attention, back to work!
-Graydon
_______________________________________________
Rust-dev mailing list
[email protected]
https://mail.mozilla.org/listinfo/rust-dev
