Skip site navigation (1) Skip section navigation (2)

Re: Time to start drafting the 8.4 release

From: Santiago Zarate <santiago(at)zarate(dot)net(dot)ve>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: pgsql-advocacy(at)postgresql(dot)org
Subject: Re: Time to start drafting the 8.4 release
Date: 2009-04-02 05:16:02
Message-ID: a37e9c560904012216r23b74fb2q5e37a0bd0c557482@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-advocacy
2009/4/1 Josh Berkus <josh(at)agliodbs(dot)com>:
> Actually, we have four basic theme ideas:
>
> 1) Smarter PG: more ability to develop "smart" applications on PG (David)
>    Pro: It's what we do as a project
>    Con: very similar to our theme last year
>
> 2) Fastest Developing Database: putting out a release *every* year, no
> matter what (Josh)
>    Pro: timely, given issues with other DBMSes
>    Con: very similar to our theme last year

Making a combination:

Releases every year, gives to developers more tools and advantages as
the (market|needs)? grows, with a wide array of features

> 3) Maturity: After many years of development, PG has become feature-complete
> in many areas. (Bruce)
>    Pro: accurate
>    Con: "maturity" ~ "stagnation"
>
> 4) BI/OLAP: focus on Windowing/Recursive.
>    Pro: industry buzzword-compliant
>    Con: don't have rest of toolset (Cube,etc.), ignores several major
> features.
>
>
> Given these, I'd think that combining (1) and (2) would probably be our best
> route.  Thoughts?
>
> --Josh
>
> --
> Sent via pgsql-advocacy mailing list (pgsql-advocacy(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-advocacy
>

In response to

pgsql-advocacy by date

Next:From: Jonathan FuerthDate: 2009-04-03 16:07:33
Subject: FreshMeat and SourceForge listings out of date again
Previous:From: Peter EisentrautDate: 2009-04-01 06:44:22
Subject: Re: Time to start drafting the 8.4 release

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group