Per discussion of various hackers at PGCon, the May commitfest is
finished.  The remaining patches on the queue are Heikki's map-forks
patch, which was WIP not intended to be committed now; and Merlin
and Andrew's libpq hooks patch, which is still in flux and not
ready to commit now.

So ... back to your regularly scheduled development.

			regards, tom lane

Tom Lane wrote:
> Per discussion of various hackers at PGCon, the May commitfest is
> finished.  The remaining patches on the queue are Heikki's map-forks
> patch, which was WIP not intended to be committed now; and Merlin
> and Andrew's libpq hooks patch, which is still in flux and not
> ready to commit now.
> 
> So ... back to your regularly scheduled development.

Is there a tag in the CVS to mark this point, or better still a tarball 
that people like me can check out and play with over the next month or two?

-- 
   Richard Huxton
   Archonet Ltd

On Wed, 2008-05-21 at 22:04 +0100, Richard Huxton wrote:

> > So ... back to your regularly scheduled development.
> 
> Is there a tag in the CVS to mark this point, or better still a tarball 
> that people like me can check out and play with over the next month or two?

That's an interesting idea. A "milestone" release. This would be
PostgreSQL 8.4 Milestone 2. Interesting advocacy and testing
implications.

Sincerely,

Joshua D. Drake

Am Mittwoch, 21. Mai 2008 schrieb Richard Huxton:
> Is there a tag in the CVS to mark this point, or better still a tarball
> that people like me can check out and play with over the next month or two?

There is not.  But the density of commits is not so high, so you should be 
able to target this state by timestamp.  Especially as there will be less 
(invasive) commits in theory during the noncommitfest times, any repository 
state between now and July is good for testing.