From owner-svn-doc-head@freebsd.org Wed Jul 22 14:44:18 2015 Return-Path: Delivered-To: svn-doc-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5B4AB9A7DCD; Wed, 22 Jul 2015 14:44:18 +0000 (UTC) (envelope-from wblock@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3FA211FCB; Wed, 22 Jul 2015 14:44:18 +0000 (UTC) (envelope-from wblock@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.70]) by repo.freebsd.org (8.14.9/8.14.9) with ESMTP id t6MEiIqH084734; Wed, 22 Jul 2015 14:44:18 GMT (envelope-from wblock@FreeBSD.org) Received: (from wblock@localhost) by repo.freebsd.org (8.14.9/8.14.9/Submit) id t6MEiIqK084733; Wed, 22 Jul 2015 14:44:18 GMT (envelope-from wblock@FreeBSD.org) Message-Id: <201507221444.t6MEiIqK084733@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: wblock set sender to wblock@FreeBSD.org using -f From: Warren Block Date: Wed, 22 Jul 2015 14:44:18 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r47040 - head/en_US.ISO8859-1/htdocs/news/status X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Jul 2015 14:44:18 -0000 Author: wblock Date: Wed Jul 22 14:44:17 2015 New Revision: 47040 URL: https://svnweb.freebsd.org/changeset/doc/47040 Log: Editing of latest reports. Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2015-04-2015-06.xml Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2015-04-2015-06.xml ============================================================================== --- head/en_US.ISO8859-1/htdocs/news/status/report-2015-04-2015-06.xml Wed Jul 22 10:48:14 2015 (r47039) +++ head/en_US.ISO8859-1/htdocs/news/status/report-2015-04-2015-06.xml Wed Jul 22 14:44:17 2015 (r47040) @@ -3034,7 +3034,7 @@ existing code. The compiler and the C library can effectively detect a set of common programming mistakes.

The current status is that a mixed version of the NetBSD and +

A mixed version of the NetBSD and Android implementations has been ported and is currently undergoing heavy testing. On &os;, this code has already found two small bugs. On the other hand, the &os; codebase @@ -3056,7 +3056,7 @@

Documentation: the framework is relatively popular on GNU - libc but we still have to work on better documentation.

+ libc but we still have to work on better documentation.

@@ -3092,16 +3092,16 @@ -

Overall, the members of the graphics team were lacking spare - time during this quarter. Thus, only few things could be +

The members of the graphics team were lacking spare + time during this quarter, and only few things could be improved.

Our ports development tree still holds an update to Mesa 10.6 - (it was 10.5 in the previous quarterly report) along with many - cleanups and bugfixes. Initially, we planned to commit it in - early July, just after FreeBSD 8.4-RELEASE EOL, but this EOL + along with many cleanups and bug fixes. (It was 10.5 in the + previous quarterly report.) Initially, we planned to commit + it in early July, just after the &os; 8.4-RELEASE end-of-life date, but the EOL was delayed to the 31st of July. Therefore, we will send a - Call For Testers near the end of July so the update can be + Call For Testers near the end of July, with the update to be committed in early August. Of course, the update can still be obtained and tested directly from the Ports development tree by using the mesa-next branch.

@@ -3120,7 +3120,7 @@

Recently, the website hosting our blog has been down frequently. It is again the case at the time of this - writing). We could export the data the last time it was up, + writing. We exported the data the last time it was up, so we will probably move to another system. Of course, the URL will change as well.