I am working on the release notes now and should be done in 1-2 days.
I am a little concerned that we still have open items with scheduled
beta ten days away. My big three items are:
o Outstanding NT issues
o Outstanding PITR issues
o Missing documentation
Right now I
On Tuesday 02 October 2001 08:32 am, Marc G. Fournier wrote:
> ftp.postgresql.org:/var/spool/ftp/pub/binary
> (216.126.85.28)
So far so good. Login successful, group membership correct. I'll let you
know if I stumble across a roadblock.
Oh, and BTW: having done server splits and moves in the
On Mon, 1 Oct 2001, Lamar Owen wrote:
> On Monday 01 October 2001 04:13 pm, Thomas Lockhart wrote:
>
> > > the only changes to directory schemes is:
> > > /var/spool/ftp/* for anon ftp
> > > /usr/local/www/www for web stuff
> > > directory structures under each should still be as
On Monday 01 October 2001 04:13 pm, Thomas Lockhart wrote:
> > the only changes to directory schemes is:
> > /var/spool/ftp/* for anon ftp
> > /usr/local/www/www for web stuff
> > directory structures under each should still be as they always were ...
> But they aren't (or didn't
...
> the only changes to directory schemes is:
> /var/spool/ftp/* for anon ftp
> /usr/local/www/www for web stuff
> directory structures under each should still be as they always were ...
But they aren't (or didn't seem to be). "find" couldn't find any
instance of the docs, unpac
On Mon, 1 Oct 2001, Thomas Lockhart wrote:
> > I agree --- for one thing, we definitely have some bugs in the datetime
> > pg_proc entries. Unless we want to go into beta with a known initdb
> > yet to do, we've got to wait for Thomas to deal with those.
>
> I had a chance to work on timestamp f
> I haven't figured out *where* the docs are supposed to go in the new
> scheme; none of the disk areas known to me on the new machines seem to
> have a documentation directory at all! Where is this stuff supposed to
> go? If things are going in different places, perhaps someone will have
> time t
> I agree --- for one thing, we definitely have some bugs in the datetime
> pg_proc entries. Unless we want to go into beta with a known initdb
> yet to do, we've got to wait for Thomas to deal with those.
I had a chance to work on timestamp features this weekend, and would
like to apply patches
"Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> we arent' ready to go beta ... I'll let you know when ...
I agree --- for one thing, we definitely have some bugs in the datetime
pg_proc entries. Unless we want to go into beta with a known initdb
yet to do, we've got to wait for Thomas to deal w
we arent' ready to go beta ... I'll let you know when ...
On Sun, 30 Sep 2001, Bruce Momjian wrote:
> > Bruce Momjian <[EMAIL PROTECTED]> writes:
> > > OK, I think we are on track for Monday beta.
> >
> > One thing that I think absolutely *must* happen before we can go beta
> > is to fix the do
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > OK, I think we are on track for Monday beta.
>
> One thing that I think absolutely *must* happen before we can go beta
> is to fix the documentation build process at hub.org. Until the online
> developer docs are up-to-date, how are beta testers go
On Sat, 29 Sep 2001, Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > OK, I think we are on track for Monday beta.
>
> One thing that I think absolutely *must* happen before we can go beta
> is to fix the documentation build process at hub.org. Until the online
> developer docs ar
Bruce Momjian <[EMAIL PROTECTED]> writes:
> OK, I think we are on track for Monday beta.
One thing that I think absolutely *must* happen before we can go beta
is to fix the documentation build process at hub.org. Until the online
developer docs are up-to-date, how are beta testers going to know
OK, I think we are on track for Monday beta. Marc, will you be
packaging a beta1 tarball on Monday or waiting a few days? I need to
run pgindent and pgjindent either right before or after beta starts.
Also, what are we doing with the toplevel /ChangeLogs. I never
understood the purpose of it,
14 matches
Mail list logo
