public inbox for [email protected]
help / color / mirror / Atom feedFrom: Joshua D. Drake <[email protected]>
To: Tom Lane <[email protected]>
Cc: [email protected]
Subject: Re: Getting a move on for 8.2 beta
Date: Fri, 01 Sep 2006 11:42:10 -0700
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
> My feeling is that we ought to bounce bitmap indexes and updatable views
> as not being ready, accept all the contrib stuff, and try to get the
> other items done in time for a beta at, say, the end of next week.
>
> I'm not thrilled about postponing those two large items till 8.3, but
> we are a month past feature freeze and we do not have credible patches
> in hand for either.
I know there is a lot of "backend" work that has been done for 8.2 but
the two features you are suggesting we bounce, are probably the most
visible of marketable features we will have for this release. Especially
updateable views.
> The alternative is to be willing to slip the
> schedule until whenever they are ready, and we have learned the hard way
> that that's not good project management.
Well I don't like the idea either, but if it isn't done, it isn't done.
How often do we hear the complaint about software that is shipped before
it is done?
Outside of feature freeze, we really haven't had AFAICS a "solid"
release schedule. Is it going to be push Beta for a month? Does that
push us till the end of the year?
I don't know which is the better solution, but you asked for comments :)
Sincerely,
Joshua D. Drake
>
> Comments?
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faq
>
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/
view thread (101+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: Getting a move on for 8.2 beta
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox