We have entered the final phases of the FreeBSD-7.0 Release cycle which
also means the beginning of the FreeBSD-6.3 Release cycle. Because the
people who support the ports for FreeBSD also need to go through a
freeze cycle as part of releases we had decided to combine the two
releases to try and minimize the impact on the ports maintainers.
The current plan is to interleave the BETAs/RCs of the 7.0 and 6.3
releases, trying to follow this for the dates when the builds will get
started (with them becoming available on the FTP mirrors a day or two
after the builds start):
7.0 6.3
BETA1 10/17 10/24
BETA2 10/31 11/7
RC1 11/14 11/21
RC2 11/28 12/5
REL 12/12 12/19
Tomorrow (10/23) the RELENG_6 branch will be marked "6.3-PRERELEASE"
to
note that we have entered the 6.3 release cycle.
The schedule dates are, as usual, tentative. At this point RELENG_6 is
pretty mature so that schedule should be fairly accurate. Being a new
branch it is at least somewhat likely the dates for 7.0 will wind up
slipping.
The 7.0-BETA1 builds have completed and are on many of the FreeBSD
mirror sites. If you want to update an existing machine using cvsup use
RELENG_7 as the branch tag. Instructions on using FreeBSD Update to
perform a binary upgrade from FreeBSD 6.x to 7.0-BETA1 will be provided
via the freebsd-stable list when available.
The MD5/SHA256 sums for the ISO files are:
MD5 (7.0-BETA1-amd64-bootonly.iso) = 8c6c02401bbd2e68d11ec554e4e1c4a2
MD5 (7.0-BETA1-amd64-disc1.iso) = 91280b705c7330225f6245c6316f6c41
MD5 (7.0-BETA1-amd64-disc2.iso) = 81dab65b611ec4ebea40f311969ad27a
MD5 (7.0-BETA1-amd64-docs.iso) = cc002beb3a69ab6245a8a70f52b3528c
MD5 (7.0-BETA1-amd64-livefs.iso) = 526554b4b5cc98b2544dd817dbf42b0c
MD5 (7.0-BETA1-i386-bootonly.iso) = a1caa2daa032294a5ab101ba7507325a
MD5 (7.0-BETA1-i386-disc1.iso) = 47929d67f5673ddd856f54811e744ac2
MD5 (7.0-BETA1-i386-disc2.iso) = 432c54565287f49a7449cb452267852e
MD5 (7.0-BETA1-i386-docs.iso) = 57e032ba93b1395a2f2bc859a8816f6a
MD5 (7.0-BETA1-ia64-bootonly.iso) = b868f5accee282cc386c419ffcf8642e
MD5 (7.0-BETA1-ia64-disc1.iso) = 59c63c6dd5a6986e30fe5cdd218b1d18
MD5 (7.0-BETA1-ia64-disc2.iso) = 9a011dafcd964a1c3e7dff689ebc5cf9
MD5 (7.0-BETA1-ia64-docs.iso) = 3bbf0db507b317a8fa3afe48b800f557
MD5 (7.0-BETA1-ia64-livefs.iso) = 93c3de935c3002a39b291b10f4c45be8
MD5 (7.0-BETA1-pc98-bootonly.iso) = b38f9676dd15308464e81172f9fbaa37
MD5 (7.0-BETA1-pc98-disc1.iso) = d00d2d92ab7b5ff248e431ff22229d11
MD5 (7.0-BETA1-sparc64-bootonly.iso) = 1a64706fe2c42d338af2f136ef57a903
MD5 (7.0-BETA1-sparc64-disc1.iso) = f72780b77fae0b841f08c2126d8e6007
MD5 (7.0-BETA1-sparc64-disc2.iso) = 0477d9547d03b97033c07efac1c1a212
SHA256 (7.0-BETA1-amd64-bootonly.iso) =
343b2b3c63daa8e99dd3cf80f2eb65a63810fc1caef7dbe74ebf54b57d4c8923
SHA256 (7.0-BETA1-amd64-disc1.iso) =
658d9ef30d07576038b8d40724851b46de1311d9ef742806c24c8b284ec72d11
SHA256 (7.0-BETA1-amd64-disc2.iso) =
c596d4f7904cb2ffca06fd9f3958dd8068cacb92fa22d57e3b53b03029eee8f6
SHA256 (7.0-BETA1-amd64-docs.iso) =
a3399826d857488b18a89f915e1397e07966d979209ed9f2f909b546764ce07a
SHA256 (7.0-BETA1-amd64-livefs.iso) =
c32eaba36056e6a5fdcfec3cb9af582c5c77d8a7594e9e552ffc974c624206e3
SHA256 (7.0-BETA1-i386-bootonly.iso) =
fb3dfc57b0fe53ac44471049cfd7ed043409387bb108d4dfaaa3b2285a2d67ae
SHA256 (7.0-BETA1-i386-disc1.iso) =
3d3eefe8c200deddafb9ed1315295ff52aa18b59429b480ae57a73bc8f4edd59
SHA256 (7.0-BETA1-i386-disc2.iso) =
05c84ab7d419e4971493eaeda953a8fbfdb2dee811528d2275e175cdc8fa2271
SHA256 (7.0-BETA1-i386-docs.iso) =
b26d5d7f2448c1e0e4f72339c25d065b83529861698a9cf3c60f165e1fa8a6a9
SHA256 (7.0-BETA1-ia64-bootonly.iso) =
3925348937423230d18ba072ef117e5343dfd02414c3a75cfa56d84cc325a1c8
SHA256 (7.0-BETA1-ia64-disc1.iso) =
8b39ce0b83e4fd04343d2a8e595bfbd7ded3abec8d4ff64dcf27ecaadc823f02
SHA256 (7.0-BETA1-ia64-disc2.iso) =
83e9e025064922449e6521ce92fcb32496fea04e271b5fe0157ca4f59c0cc5b0
SHA256 (7.0-BETA1-ia64-docs.iso) =
149e7525b6eb7157ce41139e9c7ad53625c4e287a4dbba5e257edc0dbe347dfa
SHA256 (7.0-BETA1-ia64-livefs.iso) =
54d716313a51d80b5583e2439ecac99c5e5ca67121fccc21f53b1483fa1d9178
SHA256 (7.0-BETA1-pc98-bootonly.iso) =
e79a8003786e1b031860f251c8b0dcaac8ce27c52f363fa4df7e3d19b15f3ce7
SHA256 (7.0-BETA1-pc98-disc1.iso) =
c7e11c012b3e0c4a45c965a46cbda0209d873dd8d7a56cf59af4ea3acb4776bc
SHA256 (7.0-BETA1-sparc64-bootonly.iso) =
c9d9c2baab182848af6ed6f3a3711b03ad734073a64b0c25607062bf152d2283
SHA256 (7.0-BETA1-sparc64-disc1.iso) =
8a1800bc03a6498f71fe739ac5a618b5fc1ef27d10a891cf5a9a81ff4c45bbd7
SHA256 (7.0-BETA1-sparc64-disc2.iso) =
2a2f63cf1d84b13018d77414c3f89d4da7acbb0a22653e59fda54759efbf03d7
--
Ken Smith
- From there to here, from here to | kensmith@cse.buffalo.edu
there, funny things are everywhere. |
- Theodore Geisel |
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: This is a digitally signed message part
Url :
http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20071023/42a97ee5/attachment.pgp
Abdullah Ibn Hamad Al-Marri
2007-Oct-23 06:31 UTC
7.0-BETA1 Available, 6.3-BETA1 coming soon...
----- Original Message ----> From: Ken Smith <kensmith@cse.Buffalo.EDU> > To: freebsd-stable@freebsd.org; freebsd-current@freebsd.org > Sent: Tuesday, October 23, 2007 5:21:00 AM > Subject: 7.0-BETA1 Available, 6.3-BETA1 coming soon... > > > We have entered the final phases of the FreeBSD-7.0 Release cycle which > also means the beginning of the FreeBSD-6.3 Release cycle. Because the > people who support the ports for FreeBSD also need to go through a > freeze cycle as part of releases we had decided to combine the two > releases to try and minimize the impact on the ports maintainers. > > The current plan is to interleave the BETAs/RCs of the 7.0 and 6.3 > releases, trying to follow this for the dates when the builds will get > started (with them becoming available on the FTP mirrors a day or two > after the builds start): > > 7.0 6.3 > BETA1 10/17 10/24 > BETA2 10/31 11/7 > RC1 11/14 11/21 > RC2 11/28 12/5 > REL 12/12 12/19 > > Tomorrow (10/23) the RELENG_6 branch will be marked "6.3-PRERELEASE" to > note that we have entered the 6.3 release cycle. > > The schedule dates are, as usual, tentative. At this point RELENG_6 is > pretty mature so that schedule should be fairly accurate. Being a new > branch it is at least somewhat likely the dates for 7.0 will wind up > slipping. > > The 7.0-BETA1 builds have completed and are on many of the FreeBSD > mirror sites. If you want to update an existing machine using > cvsup >use> RELENG_7 as the branch tag. Instructions on using FreeBSD Update to > perform a binary upgrade from FreeBSD 6.x to 7.0-BETA1 will be provided > via the freebsd-stable list when available. ><snip>> Ken Smith > - From there to here, from here to | >kensmith@cse.buffalo.edu> there, funny things are everywhere. | > - Theodore Geisel |Thank you Ken! Could you please have someone to put these interesting news in the main page of FreeBSD? I wish FreeBSD main page is more attractive for new users, with links to PC-BSD, and DesktopBSD ..etc ;) --- Regards, -Abdullah Ibn Hamad Al-Marri Arab Portal http://www.WeArab.Net/ __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
On Mon, 2007-10-22 at 22:21 -0400, Ken Smith wrote:> We have entered the final phases of the FreeBSD-7.0 Release cycle which > also means the beginning of the FreeBSD-6.3 Release cycle. Because the > people who support the ports for FreeBSD also need to go through a > freeze cycle as part of releases we had decided to combine the two > releases to try and minimize the impact on the ports maintainers.[...snip...] I upgraded with CVSup. It works fine. I'll wait for -RELEASE. bh@viola:~> uname -v FreeBSD 7.0-BETA1 #3: Wed Oct 24 00:58:37 KST 2007 root@viola.izb.knu.ac.kr:/usr/obj/usr/src/sys/GENERIC bh@viola:~> Thanks! -- Byung-Hee HWANG * InZealBomb "You know who I am?" -- Vito Corleone, "Chapter 1", page 52
On Mon, 2007-10-22 at 22:21 -0400, Ken Smith wrote:> The 7.0-BETA1 builds have completed and are on many of the FreeBSD > mirror sites. If you want to update an existing machine using cvsup useI've been doing some install testing of the 7.0-BETA1 i386 ISO's, and have found a small glitch or two. Where should bug reports for the BETA or RC installs be sent? Thanks, -- Wayne Chapeskie