Feature freeze date
We are 5 days away from the feature freeze date, but with the almost
week of downtime we have had, I don't think we can stick to that date.
Do we choose July 1 as feature freeze and July 15 as beta, or push beta
start to Auguest 1?
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
We are 5 days away from the feature freeze date, but with the almost
week of downtime we have had, I don't think we can stick to that date.Do we choose July 1 as feature freeze and July 15 as beta, or push beta
start to Auguest 1?
Well it would certainly be nice if CVS was working first. I am still
getting the following error:
$ cvs update
/projects/cvsroot: no such repository
- --
Greg Sabino Mullane greg@turnstep.com
PGP Key: 0x14964AC8 200306101553
-----BEGIN PGP SIGNATURE-----
Comment: http://www.turnstep.com/pgp.html
iD8DBQE+5jgyvJuQZxSWSsgRArHRAKDl582A3ntupytI/29x4dj/r6Ue8wCg88xD
6Y8n8+m31p0y5izI2mut4Zk=
=mSQQ
-----END PGP SIGNATURE-----
greg@turnstep.com wrote:
[ There is text before PGP section. ]
[ PGP not available, raw data follows ]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1We are 5 days away from the feature freeze date, but with the almost
week of downtime we have had, I don't think we can stick to that date.Do we choose July 1 as feature freeze and July 15 as beta, or push beta
start to Auguest 1?Well it would certainly be nice if CVS was working first. I am still
getting the following error:$ cvs update
/projects/cvsroot: no such repository
Yes. I am even holding some of the patches because I am not sure if it
makes sense to apply them when no one can check them. Marc says he will
have it working in 6 hours.
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
Bruce Momjian <pgman@candle.pha.pa.us> writes:
We are 5 days away from the feature freeze date, but with the almost
week of downtime we have had, I don't think we can stick to that date.
Do we choose July 1 as feature freeze and July 15 as beta, or push beta
start to Auguest 1?
I don't think a week of partial downtime justifies a month's slip.
The July 1/15 schedule seems like it might be a good plan though.
I know I'm not going to be done editing error messages by June 15 ...
Any other thoughts out there?
regards, tom lane
'k, someone please test ... should all be setup now and 'auto-updating'
hourly ...
On Tue, 10 Jun 2003, Bruce Momjian wrote:
greg@turnstep.com wrote:
[ There is text before PGP section. ][ PGP not available, raw data follows ]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1We are 5 days away from the feature freeze date, but with the almost
week of downtime we have had, I don't think we can stick to that date.Do we choose July 1 as feature freeze and July 15 as beta, or push beta
start to Auguest 1?Well it would certainly be nice if CVS was working first. I am still
getting the following error:$ cvs update
/projects/cvsroot: no such repositoryYes. I am even holding some of the patches because I am not sure if it
makes sense to apply them when no one can check them. Marc says he will
have it working in 6 hours.-- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org
On Tue, 10 Jun 2003, Tom Lane wrote:
Bruce Momjian <pgman@candle.pha.pa.us> writes:
We are 5 days away from the feature freeze date, but with the almost
week of downtime we have had, I don't think we can stick to that date.
Do we choose July 1 as feature freeze and July 15 as beta, or push beta
start to Auguest 1?I don't think a week of partial downtime justifies a month's slip.
The July 1/15 schedule seems like it might be a good plan though.
I know I'm not going to be done editing error messages by June 15 ...
July 1/15 sounds good to me as well ...
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
'k, someone please test ... should all be setup now and 'auto-updating'
hourly ...
Not quite there yet:
$cvs -d :pserver:anoncvs@anoncvs.postgresql.org:/projects/cvsroot login
Logging in to :pserver:anoncvs@anoncvs.postgresql.org:2401/projects/cvsroot
CVS password:
cvs login: authorization failed: server anoncvs.postgresql.org rejected
access to /projects/cvsroot for user anoncvs
- --
Greg Sabino Mullane greg@turnstep.com
PGP Key: 0x14964AC8 200306102252
-----BEGIN PGP SIGNATURE-----
Comment: http://www.turnstep.com/pgp.html
iD8DBQE+5pmwvJuQZxSWSsgRAkJ1AKCFCrFO3uSOZsapiELIRT3I/3j1cgCdFvwN
+G5aCJaZg4kNMLezAsQxZm8=
=t2BA
-----END PGP SIGNATURE-----
you have to give it a password ... any password, but a password non the
less ... someone else asked me this also, and if I enter no passwd, I can
get the same error message ...
On Wed, 11 Jun 2003 greg@turnstep.com wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1'k, someone please test ... should all be setup now and 'auto-updating'
hourly ...Not quite there yet:
$cvs -d :pserver:anoncvs@anoncvs.postgresql.org:/projects/cvsroot login
Logging in to :pserver:anoncvs@anoncvs.postgresql.org:2401/projects/cvsroot
CVS password:cvs login: authorization failed: server anoncvs.postgresql.org rejected
access to /projects/cvsroot for user anoncvs- --
Greg Sabino Mullane greg@turnstep.com
PGP Key: 0x14964AC8 200306102252
-----BEGIN PGP SIGNATURE-----
Comment: http://www.turnstep.com/pgp.htmliD8DBQE+5pmwvJuQZxSWSsgRAkJ1AKCFCrFO3uSOZsapiELIRT3I/3j1cgCdFvwN
+G5aCJaZg4kNMLezAsQxZm8=
=t2BA
-----END PGP SIGNATURE--------------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org
On Wed, 11 Jun 2003 12:10 pm, The Hermit Hacker wrote:
you have to give it a password ... any password, but a password non the
less ... someone else asked me this also, and if I enter no passwd, I can
get the same error message ...
The reason for the confusion might be because here:
http://developer.postgresql.org/docs/postgres/cvs.html#ANONCVS
the instructions state "You will be prompted for a password; just press
ENTER." which previously worked for me.
For those of us using anon CVS, Marc's advice works fine: password "a" works
for me and I can authenticate now.
Philip.
The Hermit Hacker <scrappy@postgresql.org> writes:
you have to give it a password ... any password, but a password non the
less ... someone else asked me this also, and if I enter no passwd, I can
get the same error message ...
The existing documentation specifies that the password for anoncvs is
empty. Can't we make it continue to work like that?
regards, tom lane
OK, feature freeze July 1, beta starts July 15.
---------------------------------------------------------------------------
The Hermit Hacker wrote:
On Tue, 10 Jun 2003, Tom Lane wrote:
Bruce Momjian <pgman@candle.pha.pa.us> writes:
We are 5 days away from the feature freeze date, but with the almost
week of downtime we have had, I don't think we can stick to that date.
Do we choose July 1 as feature freeze and July 15 as beta, or push beta
start to Auguest 1?I don't think a week of partial downtime justifies a month's slip.
The July 1/15 schedule seems like it might be a good plan though.
I know I'm not going to be done editing error messages by June 15 ...July 1/15 sounds good to me as well ...
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073