Re: [CORE] RC1 blocker issues

>> We have this issue every year and it's never ended up being a problem.
>> It's the author's or publisher's fault if they can't write their
>> articles ambiguous enough.
> 
> If the article is about 8.2 (which is likely should be to pique 
> interest) then there is only so much ambiguity that can be afforded.  
> Additionally, matching releases of articles, books and other media 
> coverage around the time of a release is common practice to and 
> publishers like it when they align.  The above statement sounds like it 
> has a "world-revolves around PostgreSQL" sentiment.  While it does on 
> this list, it doesn't elsewhere.  If it is the intention to leverage the 
> press coverage and articles for PostgreSQL's public face, then it would 
> be good to respect that even if you can't appreciate it.

+1

> 
>>> Also note that if we release between December 18th and January 3rd,
>>> we can pretty much expect no coverage from the press.
>>
>> We also have this issue every year and I still don't believe it.
>> Curiously, there is always excellent press coverage of everything else
>> between December 18th and January 3rd.
> 
> Retail and consumer press is hot then.  Business press is dead.  Don't 
> both doing a press release then, it'd be better to wait.

+1

Joshua D. Drake


> 
> // Theo Schlossnagle
> // CTO -- http://www.omniti.com/~jesus/
> // OmniTI Computer Consulting, Inc. -- http://www.omniti.com/
> 
>