Write release notes for PR #12013: Upstreaming bevy_color.

[alice-i-cecile]

bevyengine/bevy#12013 needs release notes for the upcoming Bevy release!

Original authors: @viridia, @mockersf

Please reply below if you'd like to write these notes.
While the author(s) of the PR often have the context, knowledge and motivation to draft the release notes for their feature,
anyone can contribute release notes!

---

Release notes should:

1. Clearly motivate the change.
2. Be written in a way that is understandable by the average Bevy user: some programming background and a general understanding of games.
3. Show off the coolest features of the PR. Screenshots are awesome, but elegant APIs are also welcome!
4. If this was a perf-centric PR, quantify the performance improvements. Graphs and statistics work well for this.

We can help you revise the release notes: a rough draft alone is incredibly useful :)
Your expertise is invaluable for contextualizing the changes; we'll work with you to bring the technical writing up to par.

To submit your release notes, modify ..\release-content\0.14\release-notes\12013_Upstreaming_bevy_color.md and submit a PR.
In that PR, please mention this issue with the Fixes #ISSUE_NUMBER keyphrase so it gets closed automatically.

[viridia]

This has already been done, you can close this.

Generating a ticket for each individual PR is going to be problematic in cases like bevy_color, where a single "feature" is the result of a large number of individual PRs. In the resulting release notes there's only going to be a single bevy_color "section" which aggregates all of the individual contributions.

[alice-i-cecile]

Generating a ticket for each individual PR is going to be problematic in cases like bevy_color, where a single "feature" is the result of a large number of individual PRs. In the resulting release notes there's only going to be a single bevy_color "section" which aggregates all of the individual contributions.

Yep, the plan going forward is to aggregate the PRs by marking only one for each group of features with C-Needs-Release-Note, and then finalizing that before generating issues.