From: | www(at)www(dot)postgresql(dot)com (World Wide Web Owner) |
---|---|
To: | pgsql-www(at)postgresql(dot)org |
Subject: | New News Entry |
Date: | 2003-11-06 17:59:45 |
Message-ID: | 20031106175945.039FCCF48E7@www.postgresql.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-www |
A new entry has been added to the news database.
Database Admin: http://www.postgresql.org/admin/edit_news.php?159
Submitted by: press(at)postgresql(dot)org
Headline: PostgreSQL v7.4 Release Candidate 1
Summary:
After a relatively short period for beta5, where nothing major arose, we
have just packaged up our first Release Candidate for v7.4, with the hopes
of producing a full release over the next 7 to 14 days.
Story:
After a relatively short period for beta5, where nothing major arose, we
have just packaged up our first Release Candidate for v7.4, with the hopes
of producing a full release over the next 7 to 14 days.
There is only one major change between Beta5 and RC1 that, so far, has
been reported back ... RC1 will no longer work with TCL8.0.x, due to a
change to pgtclCmds.c:
Use Tcl ByteArray objects to avoid unwanted character set
translation in libpgtcl\'s lo_read/lo_write commands. Also, deal
correctly with failure return from lo_read(). ljb and Tom Lane.
There are a few other changes that were made, affecting RI, Java and ECPG,
among others, with a full list of changes available at:
ftp://ftp.postgresql.org/pub/sources/v7.4/ChangeLog.BETA5.to.RC1
As we are in the home stretch of a full release, we encourage as many as
possible to test and report any bugs they can find, whether as part of the
build process, or running in \"real life\" scenarios.
If we\'ve heard no reports back before midnight on Thursday, we are looking
at a full code freeze, with a Final Release to happen on the following
Monday.
From | Date | Subject | |
---|---|---|---|
Next Message | Marc G. Fournier | 2003-11-06 18:14:42 | Re: Ready for release? |
Previous Message | Dave Page | 2003-11-06 17:42:38 | Re: Ready for release? |