Re: 10.0-RELEASE cycle status update

As some may have noticed, the 10.0-RELEASE cycle has slipped a bit
behind schedule.
        
> Here is where we stand at the moment:

>  - The iconv issues mentioned in a previous status update email[1] are
>    being looked at extensively.  There are a number of iconv(3) fixes
>    that have been committed to head/, which are pending MFC to stable/10
>    following the default 3-day merge period.  Those tracking -CURRENT
>    are encouraged to update their systems and report back (on -current_at_)
>    any issues.  Those awaiting the next 10.0 builds, please be patient.
>    We will have the next round of builds for the 10.0-RELEASE cycle
>    started as soon as possible.

> [1] http://lists.freebsd.org/pipermail/freebsd-stable/2013-November/075658.html

> Glen

What are the symptoms I might look for on FreeBSD-current?

Release engineering estimated dates ought to be updated on the website.

Better to wait for a solid 10.0-RELEASE than rush to a buggy release.

I am also concerned about the bug in re(4) driver.

Tom