On Tue, 29 Jun 1999, Vadim Mikheev wrote:
> Tom Lane wrote:
> >
> > Bruce Momjian <maillist@candle.pha.pa.us> writes:
> > > We are two weeks after the 6.5 release, and the anticipated
> > > problems/patches/porting issues never really materialized.
> > > I would suspect that fewer people are using PostgreSQL, but I know that
> > > is not true. Seems the two months of beta really got out the bugs.
> >
> > I think we did pretty well.
>
> First time for last two years -:)).
We must be starting to know what we are doing, eh? :)
> > > What do people want to do now? Does anyone want to start on 6.6? Do we
> > > want to release 6.5.1? Should we relax for a few more weeks and bask in
> > > the stable release?
> >
> > IMHO we do need to make a 6.5.1 release --- I know I have a couple of
> > stupid bugs in 6.5 :-(. But it is not urgent; we could wait another
> > couple of weeks and see if anything else pops up.
> >
> > Probably the nearer decision is when to split the tree for 6.6.
> > Is anyone ready to start on new stuff for 6.6? The argument that
> > we wanted to avoid double-patching is looking less compelling with
> > so few patches, so I'm ready to see a tree split as soon as anyone
> > has anything to commit into 6.6 only...
>
> I have nothing yet. But I just made changes to avoid
> disk writes for read-only transactions (now speed of
> selects is the same as with -F) - should I put it
> in 6.5.1 or wait for 6.6?
Opinion: if you feel safe, throw it in for v6.5.1.
Let's scheduale a v6.5.1 for July 15th, and a 6.6 split for, let's say,
Monday? That way those that want to can start in on 6.6, but we give a
couple of more weeks to "relax" for those that want to...
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org