On 5/29/26 12:46 PM, Robert Haas wrote:
> I do feel like this release announcement (like others you've written)
> is extremely dense, and if I were writing it myself I would probably
> mention somewhat fewer things so that the things I did mention hit
> harder, but of course I'm not: you are. I also understand that gets
> into tough arguments about what's actually worth mentioning, which are
> inevitably subjective. Still, I'd suggest as a zero-order guideline
> that including things that are <~ 500 LOC is more likely to be clutter
> than a true headline feature.
first, thank you (and everyone!) for the reviws.
I'll reply / incorporate the other comments (+ other replies) on the
thread separately, but wanted to address this one specifically.
Specifically for beta, I think we need to optimize for discoverability,
one for testing purposes, but to make people generally aware what's
available. The difference between the announcements and the release
notes is that the announcements can give more context to the features
and why they matter. In the past, we've had issues where we've missed
things that have had significant user impact, so I've biased to be more
verbose vs. less.
Now, if it's unintelligible because there's too much in there, or we
need to make room for other things that's fine. OTOH, if we're in the
"agenetic summarization" world, to me it seems better to put more detail
into the release announcement.
Flipping back to the GA I think your point does stand with an asterisk -
I think we can make those more focused and expand on a few different
features, but I do want to save that discussion for when we ramp up that
portion of the release cycle.
Thanks,
Jonathan
