Re: CURRENT vs. STABLE vs. RELEASE, tags and branches [was: Re: That age old question again]
On Mon, 17 Mar 2008 03:21:31 +0200 Giorgos Keramidas [EMAIL PROTECTED] wrote: RELENG_7 This is a branch too. It includes all development of the 7-STABLE series. Created at the same point as the release tag called RELENG_7_0_0_RELEASE, this is the basis for all the subsequent releases 'cut from the 7.X series'. RELENG_7 was actually branched 4 months before RELENG_7_0_0_RELEASE. If it hadn't been there would have been nowhere for new development to to be done. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: That age old question again
On Mon, Mar 17, 2008 at 09:18:27AM +1000, Robert Chalmers wrote: Not quite but close. On the front page of FreeBSD.org, is the download links for LATEST RELEASES a.. Production Release 7.0 Which I'm assuming is the latest, and commercially useable version. Now I still find the situation of CURRENT, STABLE as they relate to RELEASE slightly confusing, and no amount of description seems to clear it up. Ok, I understand CURRENT is developmental, and becomes the next major version as stated below. So the next major version is the one on the website? Release 7.0 - or, 7.0-RELEASE ...yes/no? Then 7.0-STABLE continues the work to be the bugfix/security blah blah tree. The question I have is: For the Production Release shown above - 7.0-RELEASE, what is the cvsup tag to keep this version updated ?? Kind of the easiest thing to do is trim the tag for how much less security you want.7.0-RELEASE gets you just that. 7 a little more fluid and HEAD is bleeding edge - is CURRENT for 7.xx. So,tag=RELENG_7_0 I think only security fixes tag=RELENG_7security fixes and stable upgrades tag=. latest additions and fixes and experiments I am a little more foggy about how the next major (8.xx) fits in to the tag values. jerry . -CURRENT is the development tree that will eventually become the next major version of FreeBSD. The developers try to keep this tree buildable, but they can't guarantee that it will be usable. Tread lightly all those that dare run this version. You must know what you are doing, understand how to debug and rebuild, and be prepared for lost data. As I write, this is known as 7-CURRENT, which will one day become FreeBSD 7.0. The cvsup tag for CURRENT is . (the period). . ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
That age old question again
Not quite but close. On the front page of FreeBSD.org, is the download links for LATEST RELEASES a.. Production Release 7.0 Which I'm assuming is the latest, and commercially useable version. Now I still find the situation of CURRENT, STABLE as they relate to RELEASE slightly confusing, and no amount of description seems to clear it up. Ok, I understand CURRENT is developmental, and becomes the next major version as stated below. So the next major version is the one on the website? Release 7.0 - or, 7.0-RELEASE ...yes/no? Then 7.0-STABLE continues the work to be the bugfix/security blah blah tree. The question I have is: For the Production Release shown above - 7.0-RELEASE, what is the cvsup tag to keep this version updated ?? . -CURRENT is the development tree that will eventually become the next major version of FreeBSD. The developers try to keep this tree buildable, but they can't guarantee that it will be usable. Tread lightly all those that dare run this version. You must know what you are doing, understand how to debug and rebuild, and be prepared for lost data. As I write, this is known as 7-CURRENT, which will one day become FreeBSD 7.0. The cvsup tag for CURRENT is . (the period). . ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: That age old question again
On Monday 17 March 2008 00:18:27 Robert Chalmers wrote: Not quite but close. On the front page of FreeBSD.org, is the download links for LATEST RELEASES a.. Production Release 7.0 Which I'm assuming is the latest, and commercially useable version. Now I still find the situation of CURRENT, STABLE as they relate to RELEASE slightly confusing, and no amount of description seems to clear it up. Ok, I understand CURRENT is developmental, and becomes the next major version as stated below. So the next major version is the one on the website? Release 7.0 - or, 7.0-RELEASE ...yes/no? Then 7.0-STABLE continues the work to be the bugfix/security blah blah tree. The question I have is: For the Production Release shown above - 7.0-RELEASE, what is the cvsup tag to keep this version updated ?? Releases are like photos: a momentum in time. Current and stable are moving targets, where current moves faster then stable. As a general rule, if something comitted in -current holds up for x weeks (I believe 3, but it ain't written in stone) and it has importance for -stable, it will be committed to stable and end up in a the next /minor/ release for that branch. Development in -current ends up in the next /major/ release. As it stands, 7 is the stable branch, 8 is the current branch and 6 is legacy stable, 5 is pray-it-still-works ancient 'stable' and 4 is passed end-of life. So far so good. Except, there's also the ability to keep a release up to date with only security fixes. That's what you want to use in production and the cvs tag contains two version numbers: RELENG_7_0. Yes, I realize many use -stable branches in production, but there is the chance that your system is broken on reboot. Reading through the dated entries in /usr/src/UPDATING gives you an idea what users of -stable can deal with and make your descision accordingly. -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: That age old question again
Robert Chalmers [EMAIL PROTECTED] wrote: Not quite but close. On the front page of FreeBSD.org, is the download links for LATEST RELEASES a.. Production Release 7.0 Which I'm assuming is the latest, and commercially useable version. Now I still find the situation of CURRENT, STABLE as they relate to RELEASE slightly confusing, and no amount of description seems to clear it up. What's so confusing? CURRENT = pure development branch for major new features ... i.e. will become 8.0 eventually. STABLE = development to the next minor release ... 7-STABLE will become 7.1 eventually, and 6-STABLE will eventually become 6.4 Ok, I understand CURRENT is developmental, and becomes the next major version as stated below. So the next major version is the one on the website? Release 7.0 - or, 7.0-RELEASE ...yes/no? CURRENT will become 8.0 when it hits release. Probably in a few years. Then 7.0-STABLE continues the work to be the bugfix/security blah blah tree. The question I have is: For the Production Release shown above - 7.0-RELEASE, what is the cvsup tag to keep this version updated ?? You want RELENG_7_0 for bugfixes/security fixes for production systems. You only want STABLE or CURRENT if you're testing the next version, assisting with development, or need a feature before it's officially released. -- Bill Moran http://www.potentialtech.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
CURRENT vs. STABLE vs. RELEASE, tags and branches [was: Re: That age old question again]
On 2008-03-17 09:18, Robert Chalmers [EMAIL PROTECTED] wrote: Not quite but close. On the front page of FreeBSD.org, is the download links for LATEST RELEASES a.. Production Release 7.0 Which I'm assuming is the latest, and commercially useable version. Now I still find the situation of CURRENT, STABLE as they relate to RELEASE slightly confusing, and no amount of description seems to clear it up. Ok, I understand CURRENT is developmental, and becomes the next major version as stated below. So the next major version is the one on the website? Release 7.0 - or, 7.0-RELEASE ...yes/no? Then 7.0-STABLE continues the work to be the bugfix/security blah blah tree. The question I have is: For the Production Release shown above - 7.0-RELEASE, what is the cvsup tag to keep this version updated ?? Hi Robert, After the 7.0-RELEASE was announced the following CVS tags became available for general use: RELENG_7_0_0_RELEASE This is a 'snapshot' of the source tree at the time of the release. No bug fixes are possible in a 'snapshot' tag. It is just a reference point, which can be used to reconstruct a copy of the source tree used to build 7.0-RELEASE. RELENG_7_0 This is a 'branch' that includes all the source files of the release snapshot and *security* fixes only. Being a 'branch' this is not a static snapshot. It may 'move' in time, pointing to newer updates for some files. Since it is a security-only branch, however, updates are expected to be minimal and are announced in freebsd-security as they become available. RELENG_7 This is a branch too. It includes all development of the 7-STABLE series. Created at the same point as the release tag called RELENG_7_0_0_RELEASE, this is the basis for all the subsequent releases 'cut from the 7.X series'. The changes which are allowed to go into this branch are a lot more than `RELENG_7_0', its associated security branch. New userland features, documentation updates, even new utilities or entirely new kernel features are all allowed, as long as compatibility with previous 7.X releases is not compromised. If you haven't read them already, the following two links are probably going to be useful: http://www.freebsd.org/doc/en_US.ISO8859-1/articles/version-guide/ http://www.freebsd.org/security/security.html#supported-branches ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
