> > Are you going to generate HISTORY from (sgml) for this release? If so, I
> > will skip updating that.
>
> Yes. So, I'm going to be out of town from this evening through the
> holiday weekend. And I would need a few days (4?; could shrink it a
> bit by taking a day from work) to prepare postscript hardcopy for a
> release.
>
> Are we on track to release June 1? If so, I'd like to derail it by a
> few days to get the hardcopy docs prepared. If not, I won't need to
> take the fall for asking for a slip ;)
No one has requested any kind of slip from June 1. I may if we can't
get these final items done on the open list. My major item is to fix
the psql \h, man pages, and docs for the new locking parameters from
Vadim. That will have to be done before the release, and I haven't done
them yet. We also need regression tests from numeric. I would say we
should target June 4 or June 7 for the release, depending on whether we
need the weekend. We are certainly in good shape for this release,
though.
>
> An alternative which I would support but am not yet as satisfied with
> would be to decouple the hardcopy docs from the release package. Then
> I could release the hardcopy a few days after the actual release.
No, no reason to do that, and once we release, we will be very busy
fielding problem reports, so it doesn't buy us anything to decouple
them.
>
> This alternative has the attractive feature that I don't need to get
> final updates two weeks in advance of a release to start prepping the
> hardcopy. Especially since I *never* manage to get those updates from
> everyone that early. html and text files like INSTALL would ship with
> the first release, since those are either automatic (html) or easy (~5
> minutes each for INSTALL or HISTORY).
Again, let's not decouple them.
-- Bruce Momjian | http://www.op.net/~candle maillist@candle.pha.pa.us | (610)
853-3000+ If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill,
Pennsylvania19026
