Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 3 Sep 2016 15:57:08 +0900
From:      Tomoaki AOKI <junchoon@dec.sakura.ne.jp>
To:        freebsd-stable@freebsd.org
Cc:        gjb@FreeBSD.org, imp@FreeBSD.org
Subject:   Re: 11.0-RELEASE status update
Message-ID:  <20160903155708.a3d6f145416d4c2c83876285@dec.sakura.ne.jp>
In-Reply-To: <20160901211000.GZ19112@FreeBSD.org>
References:  <20160901211000.GZ19112@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
Any chance for MFC'ing r304443?

  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210686

If not, the workaround should be better documented in RELNOTES.


On Thu, 1 Sep 2016 21:10:00 +0000
Glen Barber <gjb@FreeBSD.org> wrote:

> As some of you may be aware, a few last-minute showstoppers appeared
> since 11.0-RC1 (and before RC1).
> 
> One of the showstoppers has been fixed in 12-CURRENT, and merged to
> stable/11 and releng/11.0 that affected booting from large volumes:
> 
>  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212139
> 
> There is one issue that is still being investigated, which we are
> classifying as an EN candidate, given the manifestations of the issue
> and reproducibility:
> 
>  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212168
> 
> There is one blocker before 11.0-RELEASE, that affects libarchive, which
> we are waiting for feedback.  Once feedback is received, the schedule
> for 11.0-RELEASE will be updated on the website to reflect reality.
> 
> There are a few post-release EN items on our watch list as well, so if
> something was not mentioned here, that does not mean it will not be
> fixed in 11.0-RELEASE.
> 
> Apologies for the delay, and as always, thank you for your patience.
> 
> Glen
> On behalf of:	re@
> 


-- 
青木 知明  [Tomoaki AOKI]    <junchoon@dec.sakura.ne.jp>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160903155708.a3d6f145416d4c2c83876285>