freebsd stable - Oct 2004 - Plan for 5.3-RELEASE

All,

Today was supposed to be the release day for 5.3, but some serious 
show-stoppers came to light yesterday.  Since the purpose of 5.3 is to
have a functionally stable release that is suitable for migrating to,
we decided to hold up 5.3 until these issues are fixed.  The first issue
deals with TCP SACK problems that result in a livelocked system.  The
second involves GDB leaving threaded processes in an unkillable state.
Fixes for both are under review and will be committed to RELENG_5 in a
few days when preliminary testing is complete.

I've also turned off ULE to help narrow down many of the ambiguous 
problems that are still being reported.  ULE works fine for some, but
it must be eliminated from the environment when you suspect a bug.
I expect to keep ULE off in 5.x until the rate of other problem reports
and decreased and someone takes an active interest in it.

Please continue to test RC1.  At this point I'm not going to promise a
particular date for 5.3-RELEASE, but I would expect it in the next 7-10
days assuming nothing else significant comes up.

Scott

Hi Scott and lists.
With all of this, i expect to keep testing RC1, and RC2 should come
before 5.3 to be completely released.
If 5.3 is scheduled to be released in 7-10 days, you could release
-RC2 in next 3-5 days so we've the posibility to test fixed things
that might not be in current -RC1.
Just an idea.

Cya,
Martin
> All,
> Today was supposed to be the release day for 5.3, but some serious
> show-stoppers came to light yesterday.  Since the purpose of 5.3 is to
> have a functionally stable release that is suitable for migrating to,
> we decided to hold up 5.3 until these issues are fixed.  The first issue
> deals with TCP SACK problems that result in a livelocked system.  The
> second involves GDB leaving threaded processes in an unkillable state.
> Fixes for both are under review and will be committed to RELENG_5 in a
> few days when preliminary testing is complete.
> I've also turned off ULE to help narrow down many of the ambiguous
> problems that are still being reported.  ULE works fine for some, but
> it must be eliminated from the environment when you suspect a bug.
> I expect to keep ULE off in 5.x until the rate of other problem reports
> and decreased and someone takes an active interest in it.
> Please continue to test RC1.  At this point I'm not going to promise a
> particular date for 5.3-RELEASE, but I would expect it in the next 7-10
> days assuming nothing else significant comes up.
> Scott