Style Team & Stabilization Process

[calebcartwright]

Recent conversations about let chain stabilization make me think we should review how t-style ties into the stabilization process and how we communicate/share our part.

• Do we as a team still think style should be a hard blocker in the stabilization process?
• Do we think the existing singular check box suffices, or could it be split in some way? (there was a suggestion to split between t-style finalizing decision rules separate from "open PR to style guide")
• Where/how/when should we communicate decision made for new syntax? (RFC issue, tracking issue, separate style-related issue in r-l/rust, separate issue in r-l/style-team, Zulip, etc.)

Additional context

• https://rust-lang.zulipchat.com/#narrow/channel/213817-t-lang/topic/style.20specification.20as.20a.20blocker.20for.20stabilization/with/511028262
• Stabilize let chains in the 2024 edition rust#132833 (comment)
• https://github.com/rust-lang/style-team/blob/main/nightly-style-procedure.md
• https://github.com/rust-lang/rust/blob/master/src/doc/style-guide/src/nightly.md

(P.S. I initially thought to utilize #202 for this topic, but upon further review I think the question there was more related to where the in-tree text of the style guide applied.)

[calebcartwright]

Discussed in today's t-style meeting

Team agreement that we still want style to be incorporated as part of stabilization processes, proposed changes to the template to split up the check boxes (rust-lang/rust#139599) to more clearly indicate status within the existing process, and the combination of this more detailed set of checkboxes along with https://github.com/rust-lang/style-team/blob/main/nightly-style-procedure.md would cover the final question/bullet