![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
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...g.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. ---------------------------(end of broadcast)--------------------------- TIP 7: don't forget to increase your free space map settings |

#3
| |||
| |||
|
|
"MGF" == Marc G Fournier <scrappy (AT) postgresql (DOT) org> writes: |
#4
| |||
| |||
|
|
"MGF" == Marc G Fournier <scrappy (AT) postgresql (DOT) org> writes: MGF> As we are in the home stretch of a full release, we encourage as many as MGF> possible to test and report any bugs they can find, whether as part of the MGF> build process, or running in "real life" scenarios. MGF> If we've heard no reports back before midnight on Thursday, we are looking MGF> at a full code freeze, with a Final Release to happen on the following MGF> Monday. Does this now guarentee no more initdb will be required? do I have to be a major guru or coder to be on the dev list? I'd REALLY |
#5
| |||
| |||
|
|
"MGF" == Marc G Fournier <scrappy (AT) postgresql (DOT) org> writes: MGF> As we are in the home stretch of a full release, we encourage as many as MGF> possible to test and report any bugs they can find, whether as part of the MGF> build process, or running in "real life" scenarios. MGF> If we've heard no reports back before midnight on Thursday, we are looking MGF> at a full code freeze, with a Final Release to happen on the following MGF> Monday. Does this now guarentee no more initdb will be required? |
#6
| |||
| |||
|
|
do I have to be a major guru or coder to be on the dev list? |
#7
| |||
| |||
|
|
do I have to be a major guru or coder to be on the dev list? |
|
I'd REALLY like to find out what the roadmap is for Postgres, especially in relationship to locale's, sorting, and encodings. |
#8
| |||
| |||
|
|
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. |
#9
| |||
| |||
|
|
do I have to be a major guru or coder to be on the dev list? I'd REALLY like to find out what the roadmap is for Postgres, especially in relationship to locale's, sorting, and encodings. Use the news server. |
#10
| |||
| |||
|
|
Marc G. Fournier writes: 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. Folks, we still need verification of PostgreSQL 7.4 on certain platforms. See http://developer.postgresql.org/docs...platforms.html for a list of what has already been tested. In particular, if you have any of the following platforms available, IRIX NetBSD (anything but ix86) OpenBSD (anything but ix86 and sparc) SCO OpenServer ^^^^^^^^^^^^^^^^^ |
![]() |
| Thread Tools | |
| Display Modes | |
| |