All, As you probably noticed, we are a bit behind on the 5.4 release. There was a major stability problem reported several weeks ago in a particlar high load, high profile environment, and we decided that it was in everyones best interest to get it resolved before the release. Well, thanks to the tireless efforts of Doug White and Stephen Uphoff and several others, the bug has been found, fixed, and verified. As soon as it and a few other fixes get merged in, we will start the RC4 build process and hopefully release it for testing late this weekend. After that, unless another show-stopper comes up, we expect to build and release 5.4-RELEASE next weekend. Thanks for everyone's patience and work so far. When RC4 comes out please test it as much as possible so that we can ensure that 5.4 is a good release. Scott
> As you probably noticed, we are a bit behind on the 5.4 release. There > was a major stability problem reported several weeks ago in a particlar > high load, high profile environment, and we decided that it was in > everyones best interest to get it resolved before the release. Well, > thanks to the tireless efforts of Doug White and Stephen Uphoff and > several others, the bug has been found, fixed, and verified. As soon > as it and a few other fixes get merged in, we will start the RC4 build > process and hopefully release it for testing late this weekend. After > that, unless another show-stopper comes up, we expect to build and > release 5.4-RELEASE next weekend.Nice to hear. I have a four-way opteron-postgresql-server which is running low on disk-space, larger disks are right next to my desk, just waiting :-) Are there any finer details related to the four-way or larger-bug? regards Claus
On 4/30/05, Claus Guttesen <kometen@gmail.com> wrote:> > As you probably noticed, we are a bit behind on the 5.4 release. There > > was a major stability problem reported several weeks ago in a particlar > > high load, high profile environment, and we decided that it was in > > everyones best interest to get it resolved before the release. Well, > > thanks to the tireless efforts of Doug White and Stephen Uphoff and > > several others, the bug has been found, fixed, and verified. As soon > > as it and a few other fixes get merged in, we will start the RC4 build > > process and hopefully release it for testing late this weekend. After > > that, unless another show-stopper comes up, we expect to build and > > release 5.4-RELEASE next weekend. > > Nice to hear. I have a four-way opteron-postgresql-server which is > running low on disk-space, larger disks are right next to my desk, > just waiting :-) > > Are there any finer details related to the four-way or larger-bug? > > regards > Claus > ___Hi I am abit confused here, have seen a post from someone using 5.4-STABLE how is that possible if 5.4 isnt RELEASE yet, and good news on the bug fix. Chris ____________________________________________> freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" >
Hello Chris, Monday, May 2, 2005, 10:14:47 PM, you wrote these comments:> Hi I am abit confused here, have seen a post from someone using > 5.4-STABLE how is that possible if 5.4 isnt RELEASE yet, and good newsRELENG_5 has a -STABLE tag since RELENG_5_4 was branched, so if you use _5 you will get 5.4-STABLE and if you use _5_4, you will get 5.4-RC4.> on the bug fix.> Chris-- Best regards DanGer, ICQ: 261701668 | e-mail protecting at: http://www.2pu.net/ http://danger.rulez.sk | proxy list at: http://www.proxy-web.com/ | FreeBSD - The Power to Serve! [ "Be a dear and turn the shower massage head on pulsate." -- Servo ]
On 5/2/2005 3:14 PM, Chris wrote:> On 4/30/05, Claus Guttesen <kometen@gmail.com> wrote: >>>As you probably noticed, we are a bit behind on the 5.4 release. There >>>was a major stability problem reported several weeks ago in a particlar >>>high load, high profile environment, and we decided that it was in >>>everyones best interest to get it resolved before the release. Well, >>>thanks to the tireless efforts of Doug White and Stephen Uphoff and >>>several others, the bug has been found, fixed, and verified. As soon >>>as it and a few other fixes get merged in, we will start the RC4 build >>>process and hopefully release it for testing late this weekend. After >>>that, unless another show-stopper comes up, we expect to build and >>>release 5.4-RELEASE next weekend. >> >>Nice to hear. I have a four-way opteron-postgresql-server which is >>running low on disk-space, larger disks are right next to my desk, >>just waiting :-) >> >>Are there any finer details related to the four-way or larger-bug? >> >>regards >>Claus > > Hi I am abit confused here, have seen a post from someone using > 5.4-STABLE how is that possible if 5.4 isnt RELEASE yet, and good news > on the bug fix.When RELENG_5_4 was branched, RELENG_5 went from 5.4-PRERELEASE to 5.4-STABLE to reflect that it is once again open for less-restricted development. As 5.4 will be released via the RELENG_5_4 branch, it is normal and expected to have 5.4-STABLE around before 5.4-RELEASE. -- Jonathan Noack | noackjr@alumni.rice.edu | OpenPGP: 0x991D8195 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 187 bytes Desc: OpenPGP digital signature Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20050502/f3a2936d/signature.bin