[Several vendor contacts in BCC.]
For those that did not notice the website update adding the 11.2-RELEASE
cycle schedule, I apologize for sending this to public lists this late.
I thought I had done this, but apparently not.
The 11.2-RELEASE release cycle will begin April 20, 2018. The
On 12/18/2010 21:57, Kostik Belousov wrote:
I do not question your decision of upgrading or leaving the legacy version
of BIND in the legacy branch of FreeBSD src.
You know that, and I know that. :) I just wanted to be sure that no one
got the impression that anyone other than me was responsi
icular
> >>we have tried to keep the major version of the contributed software
> >>consistent throughout a given RELENG_$N branch of FreeBSD. Hopefully the
> >>reasoning for this is obvious, we want to avoid POLA violations.
> >Actually not. My own POV is that we should
branch of FreeBSD. Hopefully the
reasoning for this is obvious, we want to avoid POLA violations.
Actually not. My own POV is that we should follow the vendor release
cycle, and not the FreeBSD release cycle, for the contributed software.
I do not advocate immediate upgrade of the third-party
Just FYI, we are about a week away from starting code freeze for the
8.1-RELEASE release cycle. Since sometimes that means stable/8 gets
a little less reliable due to higher than normal levels of developer
activity I'll adjust the branch to say it is 8.1-PRERELEASE now.
The target schedul
Just a quick note to say we're beginning the release cycle for
7.3-RELEASE. Code freeze on stable/7 began now, and stable/7 has been
adjusted to say that it is 7.3-PRERELEASE to reflect that.
More details will follow but this is the current target schedule:
01/22: code f
On Tue, Jun 05, 2007 at 11:10:03PM +0100, Chris wrote:
> On 04/06/07, Doug Barton <[EMAIL PROTECTED]> 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?
> >
>
On 04/06/07, Doug Barton <[EMAIL PROTECTED]> 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,
>From Doug Barton <[EMAIL PROTECTED]>, Mon, Jun 04, 2007 at 01:55:01PM -0700:
> 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?
> You are focusing on released version num
mon <[EMAIL PROTECTED]> wrote:
> >> > > On Tue, May 29, 2007 at 09:17:57PM +1000, Peter Jeremy wrote:
> >> > > > Agreed. 6.3-RELEASE would nominally be due around July but the
> >lack
> >> > > > of any schedule on http://www.freebsd.o
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 lit
000, Peter Jeremy wrote:
> > > > Agreed. 6.3-RELEASE would nominally be due around July but the lack
> > > > of any schedule on http://www.freebsd.org/releng/ suggests that it will
> > > > be later than that. The plans to start the 7.0-RELEASE cycle will also
> &g
On 02/06/07, Brandon S. Allbery KF8NH <[EMAIL PROTECTED]> wrote:
On Jun 2, 2007, at 3:45 , Chris wrote:
> Given that Kris repeatedly tells me and others that the ports system
> is only supported on the latest freebsd release (meaning one has to be
> upgrading freebsd on their servers every few
round July but the lack
> > > of any schedule on http://www.freebsd.org/releng/ suggests that it will
> > > be later than that. The plans to start the 7.0-RELEASE cycle will also
> > > impact this.
> >
> > At BSDCan, Ken Smith mentioned that 7.0 is due to
SE would nominally be due around July but the lack
> > > > of any schedule on http://www.freebsd.org/releng/ suggests that it will
> > > > be later than that. The plans to start the 7.0-RELEASE cycle will also
> > > > impact this.
> > >
> > >
On Sat, Jun 02, 2007 at 08:45:26AM +0100, Chris wrote:
> Given that Kris repeatedly tells me and others that the ports system
> is only supported on the latest freebsd release (meaning one has to be
> upgrading freebsd on their servers every few months to get this
> support) if 7.0 and 6.3 are rele
On Jun 2, 2007, at 3:45 , Chris wrote:
Given that Kris repeatedly tells me and others that the ports system
is only supported on the latest freebsd release (meaning one has to be
upgrading freebsd on their servers every few months to get this
support) if 7.0 and 6.3 are released around the same
http://www.freebsd.org/releng/ suggests that it will
> > > be later than that. The plans to start the 7.0-RELEASE cycle will also
> > > impact this.
> >
> > At BSDCan, Ken Smith mentioned that 7.0 is due to be branched in July and
> > released in Aug/Sep, with 6.3 qu
. The plans to start the 7.0-RELEASE cycle will also
> impact this.
At BSDCan, Ken Smith mentioned that 7.0 is due to be branched in July and
released in Aug/Sep, with 6.3 quickly following (perhaps even overlapping
so as to reuse the same ports freeze).
The ports tree is not even close t
Scott Long wrote:
> Colin Percival wrote:
>> I point releases have been obsoleted by errata notices. In the past when
>> X.Y.Z-RELEASE has happened, it has been because of critical bugs in the
>> X.Y-RELEASE which there wasn't any other mechanism to fix. Now that we
>> have errata noticed and Fre
Colin Percival wrote:
Bruce A. Mah wrote:
We've done point releases in the past but only in cases where there were
severe problems and/or regressions with released versions. Look at the
announcements and release notes for 4.6.2-RELEASE and
5.2.1-RELEASE...these were the two most recent instance
On 05/29/07 17:26, Bruce A. Mah wrote:
> And that's just the src/ part. The original poster was mostly concerned
> about the X.org upgrade, which as we all know lives in the ports/ tree.
> If we were to do a "point release" we'd basically require a complete
> port freeze and package build run. I
On Tue, May 29, 2007 at 09:17:57PM +1000, Peter Jeremy wrote:
> Agreed. 6.3-RELEASE would nominally be due around July but the lack
> of any schedule on http://www.freebsd.org/releng/ suggests that it will
> be later than that. The plans to start the 7.0-RELEASE cycle will also
>
On Tue, May 29, 2007 at 01:18:51PM +0300, Abdullah Ibn Hamad Al-Marri wrote:
> Voker, I think with ports freeze still the case, they can't release a
> new version before sorting all Xorg 7.2 issues IMHO.
The freeze has been lifted. OTOH things are still settling down.
mcl
___
, it's vastly
> easier for users to run "freebsd-update fetch install" than it is for them
> to upgrade to a new release.
That's a good point. I'd be happy if we never had to do another point
release again, since we have to do probably half the work of a normal
releas
Bruce A. Mah wrote:
> We've done point releases in the past but only in cases where there were
> severe problems and/or regressions with released versions. Look at the
> announcements and release notes for 4.6.2-RELEASE and
> 5.2.1-RELEASE...these were the two most recent instances where we did
>
If memory serves me right, LI Xin wrote:
> Hi, Erik,
>
> Erik Trulsson wrote:
>> On Tue, May 29, 2007 at 11:45:15AM +0200, Volker wrote:
> [...]
>>> I know there's a release cycle for 7-CURRENT planned next June but
>>> IMHO it can be delayed for some wee
On 2007-May-29 12:29:29 +0200, Erik Trulsson <[EMAIL PROTECTED]> wrote:
>A quick release cycle for a release from -STABLE sounds like a bad idea.
>There have been enough new things that have gone into the 6-STABLE branch
>that a full release cycle seems warranted.
Agreed. 6.
Hi, Erik,
Erik Trulsson wrote:
> On Tue, May 29, 2007 at 11:45:15AM +0200, Volker wrote:
[...]
>>
>> I know there's a release cycle for 7-CURRENT planned next June but
>> IMHO it can be delayed for some weeks.
>>
>> What does the core and releng team think?
er *if* he upgrades
his ports tree. Most new users will likely not know how to do that.
>
> While reading about all that latest trouble, I think it might not be a
> bad idea to have a (quick) release cycle and release something like
> 6.2.1-RELEASE (6.3 is still TBA). I'm consider
On 5/29/07, Volker <[EMAIL PROTECTED]> wrote:
Hi!
While reading about all that latest trouble, I think it might not be a
bad idea to have a (quick) release cycle and release something like
6.2.1-RELEASE (6.3 is still TBA). I'm considering the latest X.org
upgrade being a major up
While reading about all that latest trouble, I think it might not be a
bad idea to have a (quick) release cycle and release something like
6.2.1-RELEASE (6.3 is still TBA). I'm considering the latest X.org
upgrade being a major upgrade which would justify a release cycle (@
flz: you did a great
FYI - we have begun the release cycle for FreeBSD-6.2. Code freeze on
the RELENG_6 branch started last week. For people in the habit of
tracking RELENG_6 you will start to notice various pieces of it that
start saying "6.2" for version numbers (despite 6.2 not being officially
relea
The FreeBSD-5.4 Release Cycle will begin with a code freeze one week
from today (March 2, 2005). Since the Developers tend to be a bit
more active during the week before a code freeze and the development
branch can be a bit less stable than normal due to the extra activity
we will mark the
On Wed, Dec 01, 2004 at 01:24:44PM +0100, Joan Picanyol wrote:
> * Ken Smith <[EMAIL PROTECTED]> [20041201 12:39]:
> > This is expected to be the last of the FreeBSD-4.X releases, and is
> > meant to provide current 4.X users with a little more time to migrate
> > to FreeBSD-5.X.
>
> Is it known
* Ken Smith <[EMAIL PROTECTED]> [20041201 12:39]:
> This is expected to be the last of the FreeBSD-4.X releases, and is
> meant to provide current 4.X users with a little more time to migrate
> to FreeBSD-5.X.
Is it known if this will be an "Extended Release"? Precisely, what will
be the EOL date
The release cycle for FreeBSD-4.11 will be starting shortly, with a
target release date of January 24th, 2005. A tentative schedule is
available, though not all of the dates for the various steps have been
set. Throughout the release cycle the schedule will be updated and
available here
37 matches
Mail list logo
