make an ICE-breaker group for windows/aarch64

[nikomatsakis]

Check list of things to do:

• Create a Github label ICEBreaker-Windows -- or maybe use O-windows
• Write a guide giving some high-level guidelines like Rebrand ICE-breakers, introduce Windows notification group rustc-dev-guide#739, add the ARM notification group rustc-dev-guide#740 -- PRs merged
• Configure the rust-lang/rust repository to support the ICE-breakers commands, similar to this -- Add windows group to triagebot rust#72706 -- r+'d
• Create the Windows/ARM toml file in team repo Add windows group team#347 -- merged!
• Create a sample PR for adding yourself, similar to add nikomatsakis to LLVM ICE-breakers team#140 -- Windows example team#348 -- done, also for ARM with add your_name_here to the ARM team team#358
• Write an announcement blog post
• Remove "ICE-breaker" terminology from cleanup-crew, LLVM
• Remove the ICEBreaker-LLVM label and tag all issues that had it with A-LLVM
• Update links from older blog posts about LLVM, cleanup-crew, maybe add an EDIT about the new terminology

[nikomatsakis]

Drafting blog post here: https://hackmd.io/3oMWDAyGT8-GxV5p9nLRnw

[nikomatsakis]

Branch with rustc-dev-guide additions https://github.com/nikomatsakis/rustc-guide/tree/notification-groups

[spastorino]

• Create the Windows toml file: Add windows group team#347
• Create a sample PR for adding yourself: Windows example team#348 (would need a rebase after Uplift drop-bounds lint from clippy into rustc #347 is in)
• Configure the rust-lang/rust repository to support the ICE-breakers commands: https://github.com/rust-lang/pull/72706
• Link to the sample PR: Added in @nikomatsakis blog post draft.

[eddyp]

@nikomatsakis ARM and aarch64 are two different things. I agree ARM-land nomenclature is confusing, but ARM is "all things ARM, be it no_std/std Cortex M/R/A", while aarch64 is only about the aarch64 is just the optional 64 bit architecture implemented on ARMv8 Cortex A cores.

Is there an ARM team, or is there an aarch64 team?

Sorry for the question, but for a person familiar with ARM-land, this confusion is making it difficult to decide if this info or the mechanism proposed in rust-lang/team#358 is of interest.

[nikomatsakis]

I wound up creating just an ARM team, since we're trying to create "broader" groups in an effort to keep the total number of these sorts of groups under control. Plus, folks who know a lot about aarch64 likely know a lot about ARM too, I imagine. =) Anyway, this is done for now, so closing.

[eddyp]

@nikomatsakis there are still 3 unchecked boxes in the list above. Did you want to close #358 instead?

[nikomatsakis]

Ah, thanks for pointing that out. I forgot that I had added some check-boxes for an unrelated task (renaming of ICE-breaker groups...)

[nikomatsakis]

Created #309 for those