Thread: Need vols to work on 7.4 Announcement
Folks,
Can I have 2 people who want to take charge of the 7.4 announcement? I need
some help here because I'll be out of the country for the middle of the
month.
Here's our timeline:
Today: Start working on opening paragraph,
Ask for quotes from developers
7/12: get feature list (hopefully)
Assemble press mail-to list
7/20 deadline for 1st draft of announcement
start work on "What about Windows Port/PITR"
7/25 deadline for completed announcement
7/30 or 8/1: announcement goes out and PostgreSQL 7.4 goes up.
additional vol posts at "self-serve" sites like Newsforge.
Important questions to answer:
1) Do we want to address the question of "What about the Windows Port?" in the
announcement, or just have a canned response prepared?
2) Since this release lacks "sexy" features, do we want to confine it to the
"geeky" press, such as NewsForge and Linuxtoday? I feel that we should, and
save our big press blitz for the Windows port.
--
Josh Berkus
Aglio Database Solutions
San Francisco
> 2) Since this release lacks "sexy" features, do we want to confine it to the > "geeky" press, such as NewsForge and Linuxtoday? I feel that we should, and > save our big press blitz for the Windows port. No way. This release has some excellent features - give it all we got. Chris
Chris, > No way. This release has some excellent features - give it all we got. OK, you're volunteered: I hereby appoint you to come up with a way to explain our features to ZDNet, SFGate, and the Seattle Times that will interest them. I can't think of one, but if you can, we'd all love the publicity. -- Josh Berkus Aglio Database Solutions San Francisco
On Thu, 3 Jul 2003, Josh Berkus wrote:
> Folks,
>
> Can I have 2 people who want to take charge of the 7.4 announcement? I need
> some help here because I'll be out of the country for the middle of the
> month.
>
> Here's our timeline:
>
> Today: Start working on opening paragraph,
Following is a media release I put together quickly. Its style is Big
Business. Ie, its not the kind of thing you sent to announce or
slashdot. Its the one you send to Journos. Comments?
----
The PostgreSQL Global Development Group is pleased to announce the
availability of version 7.4 of the PostgreSQL database. This
significant release represents the work of our world wide network of
developers and contributors over the last 9 months, building on the
unparalleled success of our 7.3 release in November 2002.
Significant features in the new version include:
A complete redesign of error logging and reporting, providing developers
with an SQL99 compliant mechanism for debugging and trouble shooting,
while at the same time providing users real time suggestions on how to
avoid error conditions in their applications.
A redesign of subquery handling with the IN() clause, to ensure consistent
with other subquery operations.
The implementation of SQL99 compliant Information Schema, providing
developers with database type, object and configuration information in a
standardised way.
Statement level triggers, enabling developers and users define and
customise behaviour of the database when data is stored and manipulated.
Read only transactions, which bring a greater level of security to web and
enterprise applications by protecting data from modification.
Performance improvements to data warehousing functionality.
As well as many other features.
A Timely Release
In making the release, the PostgreSQL Global Development Group had to
balance the large number of features planned for release with a consistent
release cycle, which provides loyal users with enhancements as quickly as
possible. <Insert quote from core developer reenforcing this>
<Insert quote from user(s) about business critical nature of features
released in this version>
About the PostgreSQL Global Development Group
...
More Information
Web site
Press email
----
Gavin, > > I like it. You wanna be in charge of this one? You've built a really > > good start here, especially considering that you've only had an hour! > > Sure. You da man. Check out the timeline I posted ... I won't be available to enforce it, since I'll be limited to Israeli internet cafe's July 6-15. -- Josh Berkus Aglio Database Solutions San Francisco
> A redesign of subquery handling with the IN() clause, to ensure consistent > with other subquery operations. That should be "to allow significant speed improvements" Chris
Gavin Oh, and the PGSQL client librarys are apparently now thread-safe, which is a major Apache compliance hurdle down. -- Josh Berkus Aglio Database Solutions San Francisco
On Friday 04 July 2003 02:51, Josh Berkus wrote: > Oh, and the PGSQL client librarys are apparently now thread-safe, which is > a major Apache compliance hurdle down. Josh, FWIW, libpq has been mostly thread-safe for a long time. Not to downplay the work done by Lee and others, but I've run PostgreSQL as a backend for AOLserver for 6 years. AOLserver is the original multithreaded webserver (google for NaviServer, which, in 1995, became one of if not the first commercial webserver, from day one multithreaded with database access built in, scripted with Tcl and pooled database access also from day one). AOLserver is, as of version 3.0 (four years old) dual licensed under the GPL/APL (AOLserver Public License, a variant of the Netscape/Mozilla Public License). PostgreSQL holds up extremely well driven by a multithreaded front end. I look forward to seeing what sort of performance improvement or stability improvement Lee's work will produce. As I maintain the PostgreSQL database driver for AOLserver, I look forward to seeing how I can make connections more robust with the improved threadsafeness. -- Lamar Owen WGCR Internet Radio 1 Peter 4:11