Re: (no subject)

From: Chuck Swiger (cswiger_at_mac.com)
Date: 11/29/05

  • Next message: Jim Van Fleet: "Re: Difference between RELEASE, STABLE, CURRENT (was (no subject) )"
    Date: Mon, 28 Nov 2005 22:58:02 -0500
    To: Matthew Tomsa <mtomsa@epix.net>
    
    

    Matthew Tomsa wrote:
    > What is the difference between RELEASE versions, STABLE versions, and
    > CURRENT versions? I've done some reading but I'm still a bit confused.
    > Thanks.

    -CURRENT is alpha.

    -STABLE is supposed to be the leading edge of functionality yet be stable
    enough for production use; it should be treated as a late beta. In other
    words, test it before deploying in production, because sometimes, perhaps a day
    or two per month, -STABLE contains problems or breakage.

    Every few months, the project makes an effort to stabilize the source tree
    (including ports and docs), generates a release candidate or two, and then
    pushes out a RELEASE by tagging the -STABLE branch. A -RELEASE or security
    branch is intended for production use because it has undergone such testing,
    and is updated with security patches and critical fixes only after such changes
    have been tested in -CURRENT or -STABLE.

    If you don't know what to run, run the security branch (ie, RELENG_5_4).

    -- 
    -Chuck
    _______________________________________________
    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"
    

  • Next message: Jim Van Fleet: "Re: Difference between RELEASE, STABLE, CURRENT (was (no subject) )"

    Relevant Pages

    • Re: SOL9: How-to find which package a file is in?
      ... with the latest security patches, if patching Solaris is so volatile? ... , we had an identical test machine we could use to install patches, hardware, etc. ... The test machine may not have the horsepower to support three hundred users in production but it's capable of running the application for a smaller number of users. ... Sometimes a less demanding job could be found for old test hardware that wasn't quite good enough for the developers. ...
      (comp.unix.solaris)
    • Re: Adding Front End Security Server
      ... Terry, I understand your concerns and the need for security, but one can ... It a Home User firewall. ... > After reading several articles on the SANS.org website, ...
      (microsoft.public.backoffice.smallbiz2000)
    • Re: Security Announcements & Incremental Patches
      ... >> conservative set of changes intended for our next mainstream release'. ... > generating production server for example. ... You have to get critical security ... users than FreeBSD is so far beyond naive to be an out-and-out lie. ...
      (FreeBSD-Security)
    • Re: Honeypot stats
      ... >>>security, one also has to consider the fact that Red Hat has released ... >>>with the various applications that are in production. ... > costs are going to be with that new platform. ...
      (comp.os.vms)
    • Re: SImple, easy, secure and cheap database solution for website?
      ... all I did was say more or less what you have above - unfortunately the OP seems to have stamped his feet, thrown his toys about and then stomped out of the room when he didn't get the replies he liked... ... Good help you if you think that security is just a matter if reading some civil service blurb - considering how secure some HMG IT data management has been... ... As for the idiot who thinks he can set up such a system but had to ask how to obtain a file view of a server directory, ...
      (uk.net.web.authoring)