Re: FreeBSD 5.4 release status
On Mon, 2 May 2005, Jonathan Noack wrote: 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. Casey Schaufler (ex-SGI, previously ex-Sun) gave a great talk at a workshop I was at recently relating to closed and open source release processes. One thing he pointed out that I found quite insightful is that what a development organization does is release source code and a build environment. Specifically, they release it to the release engineers, who then release a product, and may iterate some on the source product before turning it into the product. We represent that in the FreeBSD world through a notion of release engineering branches: when the developer team is ready to generate a source product, we generate a branch. It's done with the help of the release engineering team, but at some point the correlation between the source development branch and the releasee engineering branch becomes lower and they are essentially independent. Casey was careful to point out that what a release engineering team releases may be quite different from the development organization's product -- it may have custom patches, custom build changes, documentation (release notes), logos, and who knows what else. While there's overlap in these processes, and there's no cut and dry hand-off as a result of some iteration on the release process, I think this is a useful world view, and it explains why branches become -STABLE, etc. The development organization, once its cut its source release to the release engineering team, goes back to doing what it does: building software for its next release. We used to make the handoff synchronous, and we found that caused a lot of heartache. The loosely synchronous model we have now (where people are a bit restrained) appears to work better. Robert N M Watson ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 5.4 release status
On 4/30/05, Claus Guttesen [EMAIL PROTECTED] 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 [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re[2]: FreeBSD 5.4 release status
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 news RELENG_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 ] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 5.4 release status
On 5/2/2005 3:14 PM, Chris wrote: On 4/30/05, Claus Guttesen [EMAIL PROTECTED] 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 | [EMAIL PROTECTED] | OpenPGP: 0x991D8195 signature.asc Description: OpenPGP digital signature
FreeBSD 5.4 release status
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 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 5.4 release status
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 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
