DaemonForums  

Go Back   DaemonForums > Miscellaneous > Off-Topic

Off-Topic Everything else.

Reply
 
Thread Tools Display Modes
  #1   (View Single Post)  
Old 7th June 2008
Oliver_H's Avatar
Oliver_H Oliver_H is offline
Real Name: Oliver Herold
UNIX lover
 
Join Date: May 2008
Location: Germany
Posts: 427
Default more FreeBSD releases

http://lists.freebsd.org/pipermail/f...ne/042840.html

Quote:
As some of you may know the FreeBSD Project has been attempting to shift over from "Feature based releases" to "Time based releases" as far as trying to schedule them goes. Lets just say that's still a work in progress (as in doing that with FreeBSD 7.0 didn't work out so well).
Propably nice from a desktop users point of view, but to some degree I think it doesn't fit for servers so well. But your mileage may vary ;-)
__________________
use UNIX or die :-)
Reply With Quote
  #2   (View Single Post)  
Old 7th June 2008
J65nko J65nko is offline
Administrator
 
Join Date: May 2008
Location: Budel - the Netherlands
Posts: 4,125
Default

I don't regard OpenBSD as a desktop OS but it has done "Timed based releases" for years. One release at 1st of Nov, the other at 1st of May.
__________________
You don't need to be a genius to debug a pf.conf firewall ruleset, you just need the guts to run tcpdump
Reply With Quote
  #3   (View Single Post)  
Old 7th June 2008
ninjatux's Avatar
ninjatux ninjatux is offline
Real Name: Baqir Majlisi
Spam Deminer
 
Join Date: May 2008
Location: Antarctica
Posts: 293
Default

Isn't this similar to a rolling release system in that you get what the developers think is stable out of what has been implemented up to that point? If someone really needs that, then why not just run CURRENT?
__________________
"UNIX is basically a simple operating system, but you have to be a genius to understand the simplicity."
MacBook Pro (Darwin 9), iMac (Darwin 9), iPod Touch (Darwin 9), Dell Optiplex GX620 (FreeBSD 7.1-STABLE)
Reply With Quote
  #4   (View Single Post)  
Old 7th June 2008
scottro's Avatar
scottro scottro is offline
Real Name: Scott Robbins
ISO Quartermaster
 
Join Date: Apr 2008
Location: NYC
Posts: 652
Default

It's not dissimilar. How's that for sticking the old neck out?

With FreeBSD at least, at any given moment in time, especially if you are running something besides RELEASE (e.g., STABLE) you are on a rolling release system.
Reply With Quote
  #5   (View Single Post)  
Old 8th June 2008
JMJ_coder JMJ_coder is offline
VPN Cryptographer
 
Join Date: May 2008
Posts: 464
Default

Hello,

I, for one, don't like a time-based release system. It seems so "packaged", as if it is released just so they can say they have a new version - even if the only difference is the titlebars are one shade darker.

The features-based system is much better for the consumer. If a hundred new great and improved features are developed in three months, great - version 3.0 in January and 3.1 in April. If it takes you two years to revamp the TCP/IP stack to make it 1000x more secure, great - a new release two years later.

A features-based system also makes it much easier to stick to a proper UNIX version numbering system (i.e., Major.minor.revision). In a time-based system, the numbering becomes almost arbitrary.

There is certainly a divide in FOSS today over which way to go. Some groups want the bleeding edge and have constant versions coming out (i.e., Fedora). Some will only put out a new release when necessary (i.e., Slackware).

But, as I said, I prefer the features-based system. Let's not go after new just to be new.
__________________
And the WORD was made flesh, and dwelt among us. (John 1:14)
Reply With Quote
  #6   (View Single Post)  
Old 8th June 2008
TerryP's Avatar
TerryP TerryP is offline
Arp Constable
 
Join Date: May 2008
Location: USofA
Posts: 1,547
Default

I agree wit JMJ about the feature based system -- one thing I've actually liked about FreeBSD releases is the "Oh, whats cookin' new" moment ;-)

Dunno about everyone else but I tend to remember things that change in regard to releases, such as when csup became part of the system and installing cvsup (or csup) began the move into historical interest.


OpenBSDs near clockwork releases on the other hand have never let me down in the short time that I've used OpenBSD (since a lit' bit before 4.0s release). Every time I've seen a release made, I've always been proud at the notes and instructions that come along with it -- that's what I call doing it the right way. And never have I wound up screwed over and fumbling through commit messages to figure out what the without warning broke !


How the heck they do it in time for a six months schedule, I'll never figure out >_>
__________________
My Journal

Thou shalt check the array bounds of all strings (indeed, all arrays), for surely where thou typest ``foo'' someone someday shall type ``supercalifragilisticexpialidocious''.
Reply With Quote
  #7   (View Single Post)  
Old 8th June 2008
jggimi's Avatar
jggimi jggimi is offline
More noise than signal
 
Join Date: May 2008
Location: USA
Posts: 7,975
Default

Quote:
Originally Posted by TerryP View Post
...How the heck they do it in time for a six months schedule, I'll never figure out >_>
4 months of development, 2 months of robust testing.
Reply With Quote
  #8   (View Single Post)  
Old 8th June 2008
phoenix's Avatar
phoenix phoenix is offline
Risen from the ashes
 
Join Date: May 2008
Posts: 696
Default

Quote:
Originally Posted by ninjatux View Post
Isn't this similar to a rolling release system in that you get what the developers think is stable out of what has been implemented up to that point? If someone really needs that, then why not just run CURRENT?
Because a RELEASE is pretty much guaranteed to work, and everyone can be sure tat when they install X.Y-RELEASE, they all get the same stuff. Two people updating to -CURRENT at 8:05pm on Monday are not guaranteed to get the same bits. Those two alone are more than enough reason to only run -CURRENT if you know what you are doing, know what you are getting into, know how to debug things if they break, and really, really, really need a feature that is only available in -CURRENT.

For the rest of us, having a known-good, consistent, working base is nice.
__________________
Freddie

Help for FreeBSD: Handbook, FAQ, man pages, mailing lists.
Reply With Quote
  #9   (View Single Post)  
Old 8th June 2008
phoenix's Avatar
phoenix phoenix is offline
Risen from the ashes
 
Join Date: May 2008
Posts: 696
Default

Both systems (feature-based "ship when it's ready and not before" and time-based "ship whatever is working on this date") have their pros and their cons.

The biggest con for a feature-based release schedules is who gets to decide which features are the must-haves, and how long are people willing to wait to get them in shippable shape?

The biggest con with time-based release shedules is the lenght of time you select (6 months, 9 months, 12 months?), how much effective work can be done in that time (ie how much is devoted to testing, QA, and RE), and what to do when features aren't complete at the cut-off (how many times can one feature be bumped before people get mad?).

For major, revolutionary changes, feature-based schedules work better. For minor, incremental changes, time-based schedules work better. Merging the two methods (which is what I believe they are aiming for) is a good mix: a major new release every 18-ish month, a minor release every 6 months.

That way, development happens in -CURRENT, with -STABLE branches made every 18-ish months, with all the big, major changes happening there. When the new features are ready for release, they are included into the next major release (or MFC'd to previous releases if possible). And new releases are made from -STABLE (X.1, X.2, X.3) every 6-ish months with whatever new developments have occurred since the last minor release.
__________________
Freddie

Help for FreeBSD: Handbook, FAQ, man pages, mailing lists.
Reply With Quote
Old 8th June 2008
ocicat ocicat is offline
Administrator
 
Join Date: Apr 2008
Posts: 3,318
Default

Quote:
Originally Posted by phoenix View Post
...what to do when features aren't complete at the cut-off (how many times can one feature be bumped before people get mad?).
Customers can be mad in either model, so it comes down to the truthful assessment of where development is internally & project management -- managing external (customer) expectations, monitoring, assisting, & pushing the development effort, & the general management of expectations made by all.

The model used by OpenBSD has been quite successful, & both FreeBSD & NetBSD are making efforts to move in the same direction. Timed releases can be painful, but they also bring a degree of reality into the process, & help refine the release process itself. Timed releases also keeps stability firmly in the picture as amorphous development efforts aren't allowed to exist for extended periods of time.

Last edited by ocicat; 8th June 2008 at 06:55 AM.
Reply With Quote
Old 8th June 2008
Oliver_H's Avatar
Oliver_H Oliver_H is offline
Real Name: Oliver Herold
UNIX lover
 
Join Date: May 2008
Location: Germany
Posts: 427
Default

Quote:
Originally Posted by J65nko View Post
I don't regard OpenBSD as a desktop OS but it has done "Timed based releases" for years. One release at 1st of Nov, the other at 1st of May.
That's true, but then they don't care about many things and that's the big difference to FreeBSD.
__________________
use UNIX or die :-)
Reply With Quote
Old 8th June 2008
BSDfan666 BSDfan666 is offline
Real Name: N/A, this is the interweb.
Banned
 
Join Date: Apr 2008
Location: Ontario, Canada
Posts: 2,223
Default

I use OpenBSD on my desktops, seems like a "Desktop OS" to me..
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT. The time now is 07:12 AM.


Powered by vBulletin® Version 3.8.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Content copyright © 2007-2010, the authors
Daemon image copyright ©1988, Marshall Kirk McKusick