Tom Lane wrote: > Dave Page <dp...@pgadmin.org> writes: > > In this case, createdb - however, this particular case is of very > > minor impact to us. My gripe is more on the general issue of being > > potentially forced to add support for a new version and beta test > > tools in the same timeframe that PostgreSQL has for beta. > > I hear you, but really the only way we could promise that would be to > have a period before beta of nothing happening in the core project while > tools authors do their thing. That doesn't seem productive. We're > trying to get some parallelism here, not serialize all the development > and testing.
I am talking to Dave Page via IM; I think the best we can do is to focus on API changes that affect tools early in the last commit-fest and open items closing stage. The locale flags issue wasn't in the last commit-fest but rather an item that we never really resolved during primary development. We would have to be more focused on getting those nailed down earlier, rather than allow them to have the same priority as other items. I think it would also require a new "alpha" stage where we said the tool API was stable (mostly SQL and system catalogs). This wouldn't affect the psql \dfS behavior, for example, but would perhaps affect the libpq PQinitSSL() change we made last week. -- Bruce Momjian <br...@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + If your life is a hard drive, Christ can be your backup. + -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers