From owner-svn-doc-all@freebsd.org Sat Dec 29 21:34:22 2018 Return-Path: Delivered-To: svn-doc-all@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1C65D142D9AB; Sat, 29 Dec 2018 21:34:22 +0000 (UTC) (envelope-from jrm@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B6823863B2; Sat, 29 Dec 2018 21:34:21 +0000 (UTC) (envelope-from jrm@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id A9DD718D11; Sat, 29 Dec 2018 21:34:21 +0000 (UTC) (envelope-from jrm@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id wBTLYLb4072427; Sat, 29 Dec 2018 21:34:21 GMT (envelope-from jrm@FreeBSD.org) Received: (from jrm@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id wBTLYLWq072426; Sat, 29 Dec 2018 21:34:21 GMT (envelope-from jrm@FreeBSD.org) Message-Id: <201812292134.wBTLYLWq072426@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: jrm set sender to jrm@FreeBSD.org using -f From: Joseph Mingrone Date: Sat, 29 Dec 2018 21:34:21 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r52736 - head/en_US.ISO8859-1/htdocs/news/status X-SVN-Group: doc-head X-SVN-Commit-Author: jrm X-SVN-Commit-Paths: head/en_US.ISO8859-1/htdocs/news/status X-SVN-Commit-Revision: 52736 X-SVN-Commit-Repository: doc MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: B6823863B2 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-2.97 / 15.00]; local_wl_from(0.00)[FreeBSD.org]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; NEURAL_HAM_SHORT(-0.97)[-0.972,0]; NEURAL_HAM_LONG(-1.00)[-0.998,0]; ASN(0.00)[asn:11403, ipnet:2610:1c1:1::/48, country:US] X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Dec 2018 21:34:22 -0000 Author: jrm (ports committer) Date: Sat Dec 29 21:34:21 2018 New Revision: 52736 URL: https://svnweb.freebsd.org/changeset/doc/52736 Log: 2018-01-2018-09 Report: Fix grammar issues and improve clarity Approved by: bcr Differential Revision: https://reviews.freebsd.org/D18685 Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2018-01-2018-09.xml Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2018-01-2018-09.xml ============================================================================== --- head/en_US.ISO8859-1/htdocs/news/status/report-2018-01-2018-09.xml Fri Dec 28 15:41:35 2018 (r52735) +++ head/en_US.ISO8859-1/htdocs/news/status/report-2018-01-2018-09.xml Sat Dec 29 21:34:21 2018 (r52736) @@ -370,8 +370,8 @@

1. Coordination between different groups to support the upcoming 12.0 release. The timing of the OpenSSL - 1.1.1 release posed challenges, the new OpenSSL - version included API changes, many components of + 1.1.1 release posed challenges. The new OpenSSL + version included API changes, so many components of the base system and ports required changes. Staying with the older OpenSSL in 12.0 was not a feasible option, because it would have meant @@ -398,10 +398,9 @@ developer and user surveys. If there are questions that you think should be added to the survey, please discuss them on freebsd-arch@. We are - exploring ways for automated user-driven hardware - usage data to understand the changing ways our - software is used and to target better hardware - support.

+ also exploring ways to collect automated hardware-usage data. + This will help the project to understand the changing ways our + software is used and to improve hardware support.

Here are other noteworthy events (in chronological order) since the last quarterly report.