Re: release cycle



On Tue, Jun 05, 2007 at 11:10:03PM +0100, Chris wrote:
On 04/06/07, Doug Barton <dougb@xxxxxxxxxxx> wrote:
Chris wrote:

So my question remains when we have 7.0 and 6.3 both STABLE releases
will the ports tree not be supported in 6.3 a just released version of
FreeBSD?

I can't help but get the impression that you're spoiling for a fight
here, so let me ask you to take step 1, which is relax a little.

You are focusing on released version numbers when you ask about ports
support, and we generally focus on release branches. See
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvs-tags.html
for more information about that. We will be supporting ports for
RELENG_5 and _6, and RELENG_7 after it's created from what is now HEAD.

Where I think the confusion is coming in is in regards to support for
a specific version number that is older than the latest version in
that branch. For example, support for 6.1 which is an older release on
the RELENG_6 branch. We do our best to provide ports support for older
versions on currently supported branches, but it's not always possible
to do so. You can search the archives of the ports list for
information on why just supporting 3 active branches (which will be 4
after RELENG_7 is branched) for over 16,000 ports is a pretty massive
undertaking.

I hope this makes the situation more clear.

Doug

--

This .signature sanitized for your protection



This is what I had always thought until I was told otherwise recently
thanks. Not spoiling for a fight just trying to understand the
situation because it was dissapointing to be told last week that the
reason for a ommision in UPDATING was because 6.1 was not the latest
release. For this reason I wont dig up the quote I am just happy that
6.3 will be supported.

This is an orthogonal issue. Again, if you read the URL I gave
(http://www.freebsd.org/ports/) it explains that older releases on a
stable branch (whether 5.x, 6.x or soon to be 7.x) are not supported,
although they may continue to work and we will accept patches from the
user community to keep them working when they are accidentally broken
by a change.

Kris
_______________________________________________
freebsd-stable@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe@xxxxxxxxxxx"



Relevant Pages

  • [PATCH 06/13] Char: cyclades, overall cleanup
    ... * Prevent users from opening non-existing Z ports. ... * Implemented full support for non-standard baud rates. ... * Driver now reports physical instead of virtual memory addresses. ... * Fixed SMP locking in Cyclom-Y interrupt handler. ...
    (Linux-Kernel)
  • [PATCH 13/79] cyclades: overall cleanup
    ... * Prevent users from opening non-existing Z ports. ... * Implemented full support for non-standard baud rates. ... * Driver now reports physical instead of virtual memory addresses. ... * Fixed SMP locking in Cyclom-Y interrupt handler. ...
    (Linux-Kernel)
  • Re: CLARITY re: challenge: end of life for 6.2 is premature with buggy 6.3
    ... My main drama with FreeBSD is that ports don't have -SECURITY patches, and if I there is a bug in php ... Another _very important_ thing is that there is no binary support to packages that has vulns, ... care much about stability, they are mainly interested in hacking on the ... for people who are running mission critical systems. ...
    (freebsd-stable)
  • Re: FreeBSD 5.1 support for Dell Integrated audio?
    ... I've included my config file and dmesg output below. ... # Floating point support - do not disable. ... pci0: ... 2 ports with 2 removable, ...
    (freebsd-questions)
  • Re: FreeBSD 5.1 support for Dell Integrated audio?
    ... I've included my config file and dmesg output below. ... # Floating point support - do not disable. ... pci0: ... 2 ports with 2 removable, ...
    (freebsd-questions)