DragonFly commits List (threaded) for 2007-05
Re: cvs commit: src/sys/conf subvers-RELEASE_1_4
:On Wed, 9 May 2007 11:31:02 -0700 (PDT)
:Simon Schubert <email@example.com> wrote:
:What is the EOL of 1.4.x?
:Or isn't there any policy for this?
:Gergo Szakal <firstname.lastname@example.org>
There is no specific support beyond the current head and release branches,
though any submitted MFCs for older branches will certainly be accepted.
Generally fixes will not go back more then two RELEASEs but sometimes
they will be MFCd back further.
It's usually best to just upgrade the machine to a more recent RELEASE.
As long as you are within two RELEASEs you'll be ok. So, e.g. are
current release is 1.8, so 1.6 and 1.8 will both be maintained. When
we go to 2.0, then 1.8 and 2.0 will both be maintained.
DragonFly only does two releases a year (verses the three or more
that FreeBSD does, unless they changed their policy recently). Most
of the new work is not visible to userland, except for apps which access
kmem, so maintainance of a DragonFly system is fairly straightforward.