Suggestions for both
https://wiki.debian.org/Teams/ReleaseTeam/ReleaseCheckList
https://wiki.debian.org/Teams/ReleaseTeam/ReleaseCheckList/BookwormCheckList


  Before the release

Add "Notify the LTS team of the new debian-archive-keyring"


  After the release
    [ ] Propose a micronews item on the #debian-publicity IRC channel

Should this be a subitem of "Notify the publicity team"
in "While Releasing"?


  After the release
    [ ] Update the Project History document and upload to stable-p-u

This could be moved to (and uploaded) "Before the release".


  After the release
    [ ] Check with udd maintainers that the hardcoded values are updated (see SuitesAndReposExtension#udd)
    [ ] Check with buildd team that buildds know about trixie. (see SuitesAndReposExtension#wanna-build)

IMHO these should be moved to "Before the release", otherwise there might be
stress for people who realize at short notice that urgent work has to be done.


  After the release
    [ ] Check with other service/package maintainers that all the other hardcoded suite names or codenames are updated

IMHO this should be moved to "Before the release", otherwise there might be
stress for people who realize at short notice that urgent work has to be done.

It should link to SuitesAndReposExtension, or be replaced with a list whom to notify,

Hi Adrian,

They are Wiki's ;). But thanks for discussing it first.

Do you have an example e-mail? Would everybody in the LTS team know what
this means for them (I don't).

Again, maybe an example? I'm not sure what you expect here from us.

I guess that makes sense.

Are you sure? That means we'd be predicting the future in a history
document. I guess you mean once the date is fixed and assuming we
release on schedule.

But these things can't be *done* before the release, right? So maybe
*add* a "notify" on these topics?

Incomplete sentence?

Paul