Announcing the Release Team

sgrif · 2018-01-16T02:53:40.800Z

I would be interested in helping out with this

PramodBisht · 2018-01-16T04:11:18.273Z

I am also interested.

alexcrichton · 2018-01-16T05:33:31.639Z

I’d be interested in helping out!

stokhos · 2018-01-16T05:47:04.179Z

Im interested!

dirtybit · 2018-01-16T05:48:23.527Z

Count me in! I’d love to contribute.

pambihira · 2018-01-16T08:06:14.938Z

How may i help?

cssivision · 2018-01-16T10:00:48.520Z

Interested

ArazAbishov · 2018-01-16T10:38:21.464Z

I would be happy to join the team as well

Aaronepower · 2018-01-16T11:59:16.606Z

I’m interested.

Lubits · 2018-01-16T12:56:09.107Z

I’m interested!

treiff · 2018-01-16T13:38:19.327Z

I’m definitely interested!

steveklabnik · 2018-01-16T15:40:23.321Z

I currently write the release blog post; I don’t think I have bandwidth to get involved more, but would like to at least work with the team regarding that stuff. So include me in whatever capacity you think makes sense.

BatmanAoD · 2018-01-16T18:07:45.401Z

I am interested! I’m somewhat concerned that I’ll find I don’t have the bandwidth and/or knowledge to contribute meaningfully, but I’d like to at least try.

steveklabnik:

I currently write the release blog post…

Would you like assistance with this in some way? I believe I am a fairly clear writer, and this would be a good way to keep myself up-to-date on Rust’s evolution.

adrq · 2018-01-16T20:27:47.398Z

I would definitely like to contribute. I’m looking forward to being more involved in this community!

nikomatsakis · 2018-01-16T21:21:54.154Z

One thing that @arielb1 and I were talking about in #rustc was that there is a lot of work that goes into tracking down regressions where the compiler team could really use some help.

Examples include:

Trying to narrow down to small, independent test cases (or at least reproducible ones)
Bisection
Classifying more clearly as a “compiler vs libs” issue

Do you think this ought to fall under the purview of the release team?

arielb1 · 2018-01-16T21:26:07.045Z

nikomatsakis:

Do you think this ought to fall under the purview of the release team?

Also, helping communicate solutions with issue posters (e.g. for soundness warnings, helping find the best way to fix them).

steveklabnik · 2018-01-17T22:21:40.242Z

At the moment, I don’t need any particular help! As long as release notes exist, it’s not too bad. But I’ll give it some thought…I really appreciate your interest.

Mark_Simulacrum · 2018-01-18T21:55:25.554Z

Okay, I’ve compiled a document for everyone to sign up in if they’re interested in weekly triage of Crater and issues.

Don’t worry if you aren’t interested in any of the current jobs, we’ll have more soon. Also, please message me privately on IRC or email me (mark.simulacrum at gmail.com) with your email so we can add you to the release@rust-lang.org mailing list for future announcements. Thanks!

Let me know if you have any questions or concerns.

Mark_Simulacrum · 2018-01-19T18:57:17.768Z

Everyone in this thread who expressed interest in being involved should have received an invite to the rust-lang/release team, and upon joining, you should have the ability to label issues in rust-lang/rust. So the rotation can get started next week!

xusss · 2018-01-23T02:12:01.783Z

I am interested in this work!