Josh Berkus wrote:
> No can do. A press release only "works" if it has impact, which
> means, among other things, keeping the contents relatively under
> wraps until it's officially launched.
Another feature of a press release is that those in whose name it is
made know what they are committing to. If only, say, three people know
what is going to be announced, then you can make the announcement in
the name of those three people, but not in the name of "the PostgreSQL
project". Otherwise you're just lying.
> Not everybody is involved in every patch that gets added to the code;
> not everyone will be involved in every press release.
You're wrong. Everyone has a chance to review every patch and discuss
every patch in public before it is released.
