On Thu, Apr 11, 2024 at 07:50:29AM +0200, Thorsten Leemhuis wrote: > On 11.04.24 07:30, Greg Kroah-Hartman wrote: > > On Thu, Apr 11, 2024 at 07:25:05AM +0200, Thorsten Leemhuis wrote: > >> > >> - Cc: <stable@xxxxxxxxxxxxxxx> # after 4 weeks in mainline > >> + Cc: <stable@xxxxxxxxxxxxxxx> # after 6 weeks in a stable mainline release > > > > I do not know what "stable mainline release" means here, sorry. "after > > 4 weeks in mainline" means "after in Linus's tree for 4 weeks, but > > Linus's tree is not "stable mainline". > > I meant a proper mainline release like 6.7 or 6.8 to make it obvious > that this does not mean a "pre-release". > > I actually had used the term "proper mainline release" earlier in a > draft, but a quick search on the net showed that this is not really used > out there. "stable mainline release" is not popular either, but seemed > to be a better match; I also considered "final mainline release", but > that felt odd. > > It feels like there must be some better term my mind just stumbles to > come up with. Please help. :-D Well, what is the goal here? Just put it in words, I have seen stuff like: Cc: <stable@xxxxxxxxxxxxxxx> # wait until -rc3 Cc: <stable@xxxxxxxxxxxxxxx> # wait until 6.1 is released Cc: <stable@xxxxxxxxxxxxxxx> # after -rc2 and so on. Just pick a specific time/release might be better? "after X weeks" is assuming that we all know and remember how many weeks something happened... thanks, greg k-h
