From owner-svn-doc-all@freebsd.org Mon Dec 24 10:07:28 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 6812D133CF99; Mon, 24 Dec 2018 10:07:28 +0000 (UTC) (envelope-from trasz@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 1883377EC0; Mon, 24 Dec 2018 10:07:28 +0000 (UTC) (envelope-from trasz@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 0D8C222E44; Mon, 24 Dec 2018 10:07:28 +0000 (UTC) (envelope-from trasz@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id wBOA7SYg071973; Mon, 24 Dec 2018 10:07:28 GMT (envelope-from trasz@FreeBSD.org) Received: (from trasz@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id wBOA7R3j071972; Mon, 24 Dec 2018 10:07:27 GMT (envelope-from trasz@FreeBSD.org) Message-Id: <201812241007.wBOA7R3j071972@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: trasz set sender to trasz@FreeBSD.org using -f From: Edward Tomasz Napierala Date: Mon, 24 Dec 2018 10:07:27 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r52717 - head/en_US.ISO8859-1/htdocs/news/status X-SVN-Group: doc-head X-SVN-Commit-Author: trasz X-SVN-Commit-Paths: head/en_US.ISO8859-1/htdocs/news/status X-SVN-Commit-Revision: 52717 X-SVN-Commit-Repository: doc MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 1883377EC0 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-2.98 / 15.00]; local_wl_from(0.00)[FreeBSD.org]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; NEURAL_HAM_SHORT(-0.98)[-0.983,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: Mon, 24 Dec 2018 10:07:28 -0000 Author: trasz Date: Mon Dec 24 10:07:27 2018 New Revision: 52717 URL: https://svnweb.freebsd.org/changeset/doc/52717 Log: Add Quarterly Status Report for 2018Q3. Reviewed by: allanjude, bcr (mentors) Approved by: allanjude, bcr (mentors) Differential Revision: https://reviews.freebsd.org/D18639 Added: head/en_US.ISO8859-1/htdocs/news/status/report-2018-01-2018-09.xml (contents, props changed) Modified: head/en_US.ISO8859-1/htdocs/news/status/Makefile Modified: head/en_US.ISO8859-1/htdocs/news/status/Makefile ============================================================================== --- head/en_US.ISO8859-1/htdocs/news/status/Makefile Mon Dec 24 08:12:04 2018 (r52716) +++ head/en_US.ISO8859-1/htdocs/news/status/Makefile Mon Dec 24 10:07:27 2018 (r52717) @@ -80,6 +80,7 @@ XMLDOCS+= report-2017-01-2017-03 XMLDOCS+= report-2017-04-2017-06 XMLDOCS+= report-2017-07-2017-09 XMLDOCS+= report-2017-10-2017-12 +XMLDOCS+= report-2018-01-2018-09 XSLT.DEFAULT= report.xsl Added: head/en_US.ISO8859-1/htdocs/news/status/report-2018-01-2018-09.xml ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ head/en_US.ISO8859-1/htdocs/news/status/report-2018-01-2018-09.xml Mon Dec 24 10:07:27 2018 (r52717) @@ -0,0 +1,3374 @@ + + + + + + + + + + %%START%%-%%STOP%% + + %%YEAR%% + + +
+ Introduction + +

With &os; having gone all the way to 12, it is perhaps + useful to take a look back at all the things that have been + accomplished, in terms of many visible changes, as well as all + the things that happen behind the scenes to ensure that &os; + continues to offer an alternative in both design, + implementation, and execution.

+ +

The things you can look forward to reading about are too + numerous to summarize, but cover just about everything from + finalizing releases, administrative work, optimizations + and depessimizations, features added and fixed, and many areas + of improvement that might just surprise you a little.

+ +

Please have a cup of coffee, tea, hot cocoa, or other beverage + of choice, and enjoy this culmulative set of reports covering + everything that's been done since October, 2017.

+ +

—Daniel Ebdrup

+
+ + + team + + &os; Team Reports + +

Entries from the various official and semi-official teams, + as found in the Administration + Page.

+ + + + proj + + Projects + +

Projects that span multiple categories, from the kernel and userspace + to the Ports Collection or external projects.

+ + + + arch + + Architectures + +

Updating platform-specific features and bringing in support + for new hardware platforms.

. + + + + ports + + Ports + +

Changes affecting the Ports Collection, whether sweeping + changes that touch most of the tree, or individual ports + themselves.

+ + + + doc + + Documentation + +

Noteworthy changes in the documentation tree or new external + books/documents.

+ + + + third + + Third-Party Projects + +

Many projects build upon &os; or incorporate components of + &os; into their project. As these projects may be of interest + to the broader &os; community, we sometimes include brief + updates submitted by these projects in our quarterly report. + The &os; project makes no representation as to the accuracy or + veracity of any claims in these submissions.

+ + + + Release Engineering Team + + + + FreeBSD Release Engineering Team + re@FreeBSD.org + + + + + FreeBSD 10.4-RELEASE announcement + FreeBSD 11.2-RELEASE announcement + FreeBSD 12.0-RELEASE schedule + FreeBSD development snapshots + + + +

The FreeBSD Release Engineering Team responsibilities + include:

+ +
    +
  • setting and publishing release schedules for official + project releases
    • +
+ +

of FreeBSD

+ +
    +
  • announcing code slushes, freezes, and thaws
    • + +
  • maintaining the respective branches for all supported + releases
    • +
+ +

+ The FreeBSD Release Engineering Team, led by Marius + Strobl, + completed the 10.4-RELEASE in early October 2017. FreeBSD + 10.4-RELEASE was the + fifth release from the stable/10 branch, which + built on the + stability and reliability of 10.3-RELEASE.

+ +

The FreeBSD 11.2-RELEASE cycle started April 20, 2018 with + the + announcement of the code slush. The first stage progress + was + continued throughout the rest of the quarter with the code + freeze, + followed by three BETA builds, three RC builds, and the + final release + build was announced June 27, 2018.

+ +

The FreeBSD Release Engineering Team started the + 12.0-RELEASE cycle + August 10, 2018 with the announcement of the code slush. + The code + freeze followed on August 24, 2018. The tentative date for + the stable/12 branch was expected to be September 21, + 2018.

+ +

+ Due to unforeseen circumstances with upstream code that + was necessary + to include in 12.0-RELEASE, the tentative release schedule + needed + to be adjusted several times. The API changes in the + updated version + of the upstream code required changes to be made for all + base system + utilities that linked with the upstream code. By the end + of the + 2018Q3 quarter, the stable/12 branch had not been + created due to + this delay.

+ +

Throughout the remainder of 2018Q3, several development + snapshots builds + were released for the head, stable/11, + and stable/10 branches.

+ +

Much of this work was sponsored by the FreeBSD Foundation.

+ + + + + + + Ports Collection + + + + René Ladan + portmgr-secretary@FreeBSD.org + + + + + About FreeBSD Ports + Contributing to ports + FreeBSD ports monitoring + Ports Management Team + FreeBSD portmgr (@freebsd_portmgr) + FreeBSD Ports Management Team (Facebook) + FreeBSD Ports Management Team (Google+) + + + +

During the first quarter of 2018, the number of ports grew + to almost 32,000. + In 2018Q1, there were + 2,100 open PRs with fewer than 600 unassigned. There were + 7,900 commits from 169 committers. Compared to last + quarter, the number + of commits grew by 18% and the number of PRs dropped by + 25%. Those are + some good numbers!

+ +

During the 2018Q2 and 2018Q3 quarters, the number of ports + grew to just under + 34,000. The number of open PR grew to almost 2,500 with + fewer than 600 + of those unassigned. A total of 175 committers made almost + 14,200 commits. + Compared to the first quarter, the number of commits + dropped by 10% and + the number of PRs grew by 19%.

+ +

During the last three quarters, portmgr took twelve commit + bits in for + safekeeping: daichi@, deichen@, ian@, junovitch@, kevlo@, + maho@, nemysis@, + pawel@, rea@, tabthorpe@, vg@, and wxs@.

+ +

Portmgr welcomed thirteen new committers in 2018Q2 and + 2018Q3:

+ +
    +
  • Devin Teske (dteske@)
    • + +
  • Eric Turgeon (ericbsd@)
    • + +
  • Fernando Apesteguía (fernape@)
    • + +
  • Fukang Chen (loader@)
    • + +
  • Gleb Popov (arrowd@)
    • + +
  • Jesper Schmitz Mouridsen (jsm@)
    • + +
  • John Hixson (jhixson@)
    • + +
  • Kevin Bowling (kbowling@)
    • + +
  • Koichiro IWAO (meta@)
    • + +
  • Mateusz Piotrowski (0mp@)
    • + +
  • Matthias Fechner (mfechner@)
    • + +
  • Sergey Kozlov (skozlov@)
    • +
+ +

+ The following committers returned after a hiatus:

+ +
    +
  • Ion-Mihai Tetcu (itetcu@)
    • + +
  • Kevin Lo (kevlo@)
    • + +
  • Sean Chittenden (seanc@)
    • +
+ +

+ During the last three quarters, Antoine Brodin (antoine@) + ran no + fewer than 113 exp-runs against the ports tree. These runs + were + executed to test updates, perform cleanups, and make + improvements + to the framework and the base system. Most of the runs + were for + port upgrades, but others include LLD progress, changes to + the + default port versions, improved support for armv6, armv7, + and RISC-V + architectures, removed old base system functionality, new + USES, and + better matching pkg-plist with Makefile options (DOCS and + EXAMPLES).

+ +

Five new USES values were introduced:

+ +
    +
  • apache: handle dependencies on the Apache web server and + modules
    • + +
  • eigen: automatically depend on math/eigen2 or math/eigen3
    • + +
  • emacs: handle dependencies on the Emacs editor and + modules.
    • + +
  • gl replaces the old USE_GL from bsd.port.mk
    • + +
  • qt-dist, qt:4 and qt:5 replace the old USE_QT from + bsd.qt.mk
    • +
+ +

+ The EXTRA_PATCHES functionality has been extended to + support + directories, where it will automatically apply all + patch-\* files to the port.

+ +

Ports using USES=php:phpize, php:ext, php:zend, and + php:pecl have + been flavored and packages are now automatically built + for all + versions of PHP that are supported (5.6, 7.0, 7.1 or 7.2).

+ +

2018Q3 had updates of major ports: pkg 1.10.5, Chromium + 65.0.3325.181, Firefox 59.0.2, Firefox-ESR 52.7.3, Ruby + 2.3.7/2.5.1 + and Qt5 5.9.4. + The default version of PHP was changed from 5.6 to 7.1. + The former + version of PHP is no longer supported by the developers. + The + default versions of Samba and GCC are now respectively 4.7 + and 7. The + Xorg ports have been reorganized and there have been + changes to + net/openntpd. Please review the UPDATING file for relevant + details.

+ +

Open tasks:

+ +
    +
  • The number of commits dropped somewhat over the last three + quarters, + leaving more PRs unresolved. If possible, please pick up + some PRs + and improve everyone's experience.
    • +
+ + + + + + + Core Team + + + + FreeBSD Core Team + core@FreeBSD.org + + + + +

Much of Core's focus for the past months has been on three + items:

+ +

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 + 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 + backporting many changes to a version of OpenSSL + that would be unmaintained by the upstream source.

+ +

2. Discussions with the release engineering team and Scott + Long about updating the FreeBSD release process. + Topics for exploration include:

+ +
    +
  • having more frequent point releases
    • + +
  • changing the support model
    • + +
  • revising and improving the tooling used to manage the tree + and releases
    • + +
  • additional topics as they are discovered
    • +
+ +

3. Gathering information to make decisions more + data-driven. For example, we are planning + 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.

+ +

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

+ +

2017 Q4

+ +
    +
  • Sean Eric Fagan's (sef@) commit bit was reactivated with a + period of re-mentoring under Alexander Motin + (mav@).
    • + +
  • The MIPS architecture was promoted to tier 2 status.
    • + +
  • Core approved changes to the Code of Conduct.
    • + +
  • All fortune data files, except freebsd-tips, were removed + in r325828.
    • + +
  • Core approved the adoption of a policy requiring any + license exceptions to be recorded alongside code.
    • + +
  • Gordon Tetlow (gordon@) became the new security officer.
    • + +
  • Core approved the use of SPDX tags.
    • +
+ +

+ 2018 Q1

+ +
    +
  • Jeb Cramer (jeb@) was awarded a src commit bit under the + mentorship of Sean Bruno (sbruno@) and Eric Joyner + (erj@).
    • + +
  • Members of the CoC Review Team were approved. The + membership is to be reviewed once per year.
    • + +
  • A vendor commit bit was awarded to Slava Shwartsman + (slavash@) of Mellanox Technologies under the + mentorship of Konstantin Belousov (kib@) and Hans + Petter Selasky (hselasky@).
    • + +
  • Walter Schwarzenfeld was awarded project membership.
    • + +
  • Brad Davis (brd@) was awarded a src commit bit under the + mentorship of Allan Jude (allanjude@) with + Baptiste Daroussin (bapt@) as co-mentor.
    • + +
  • Vincenzo Maffione (vmaffione@) was awarded a src commit + bit under the mentorship of Hiroki Sato (hrs@).
    • + +
  • Ram Kishore Vegesna (ram@) was awarded a src commit bit + under the mentorship of Kenneth D. Merry (ken@) + and Alexander Motin (mav@).
    • +
+ +

2018 Q2

+ +
    +
  • Tom Jones (thj@) was awarded a src commit bit under the + mentorship of Jonathan T. Looney (jtl@).
    • + +
  • Matt Macy's (mmacy@) commit bit was restored under the + mentorship of Sean Bruno (sbruno@).
    • + +
  • Breno Leitao (leitao@) was awarded a src commit bit under + the mentorship of Justin Hibbits (jhibbits@) with + Nathan Whitehorn (nwhitehorn@) as co-mentor.
    • + +
  • Leandro Lupori (luporl@) was awarded a src commit bit + under the mentorship of Justin Hibbits (jhibbits@) + with Nathan Whitehorn (nwhitehorn@) as co-mentor.
    • + +
  • The handover from the ninth to the tenth elected Core team + took place. The tenth Core members are: Allan Jude + (allanjude@), Benedict Reuschling (bcr@), Brooks + Davis (brooks@), Hiroki Sato (hrs@), Warner Losh + (imp@), Jeff Roberson (jeff@), John Baldwin + (jhb@), Kris Moore (kmoore@), and Sean Chittenden + (seanc@).
    • + +
  • Joseph Mingrone (jrm@) was appointed the Core secretary + under mentorship of the retiring Core secretary, + Matthew Seaman (matthew@).
    • + +
  • The new team liaisons were decided. portmgr: Sean, doceng: + Hiroki, secteam: Brooks, re: John, clusteradm: + Allan, CoC: Warner, Foundation: Benedict, + bugmeister: John, CI: Sean.
    • + +
  • David Maxwell (dwm@) was awarded project membership.
    • + +
  • Daichi Goto's (daichi@) commit bit was reactivated with a + period of re-mentoring under George Neville-Neil + (gnn@).
    • + +
  • A vendor commit bit was awarded to Ben Widawsky + (bwidawsk@) of Intel under the mentorship of Ed + Maste (emaste@).
    • +
+ +

+ 2018 Q3

+ +
    +
  • Core decided to begin meeting twice per month in an + attempt to catch up with many new agenda items.
    • + +
  • Li-Wen Hsu (lwhsu@) was awarded a src commit bit under the + mentorship of Mark Johnston (markj@) with Ed Maste + (emaste@) as co-mentor.
    • + +
  • Samy al Bahra was awarded project membership.
    • + +
  • George Neville-Neil (gnn@) was approved to begin + co-mentoring Vincenzo Maffione (vmaffione@).
    • +
+ + + + + + + The FreeBSD Foundation + + + + Deb Goodkin + deb@FreeBSDFoundation.org + + + + +

The FreeBSD Foundation is a 501(c)(3) non-profit + organization dedicated to supporting and promoting + the FreeBSD Project and community worldwide. + Funding comes from individual and corporate + donations and is used to fund and manage software + development projects, conferences and developer + summits, and provide travel grants to FreeBSD + contributors. The Foundation purchases and + supports hardware to improve and maintain FreeBSD + infrastructure and provides resources to improve + security, quality assurance, and release + engineering efforts; publishes marketing material + to promote, educate, and advocate for the FreeBSD + Project; facilitates collaboration between + commercial vendors and FreeBSD developers; and + finally, represents the FreeBSD Project in + executing contracts, license agreements, and other + legal arrangements that require a recognized legal + entity.

+ +

Here are some highlights of what the FreeBSD Foundation + did to help FreeBSD last quarter:

+ +

Partnerships and Commercial User Support

+ +

As a 501(c)(3) non-profit, we don't directly support + commercial users, but we do work with them to + understand their needs and help facilitate + collaboration with the community. Last quarter we + met with a few key FreeBSD users and supporters, + to discuss pain points, how they can contribute + back to FreeBSD, and what technologies they would + like to see supported, to support FreeBSD over + more of their technologies and products.

+ +

As many of you know, we formed a partnership with Intel + around one and a half years ago. Since then the + people we worked directly with left the company, + but it moved us into a new relationship with their + Open Source Technology Center (OTC).

+ +

We are very encouraged that Intel has dedicated additional + resources from the OTC to work on FreeBSD in + addition to existing resources from the networking + group and other technologies such as QuickAssist. + Much of the work has been focused on security and + OS mitigations but we're also focusing on other + areas such as power management and persistent + memory. In May and again in July we traveled to + Intel's Hillsboro campus to meet with management + and engineers from OTC and the networking team. We + presented an overview of the project and + Foundation and also discussed key markets and + vendors who use FreeBSD in their products or + services and their future requirements.

+ +

Intel was also interested in learning more about who + contributes to FreeBSD. Along those lines we've + done some work with OTC to create scripts and + organizational mappings to answer that question. + Note that we do need developers + to help us update and maintain the organizational + mappings as we understand that developers do tend + to move around and contractors are often working + on behalf of multiple organizations.

+ +

Fundraising Efforts

+ +

Our work is 100% funded by your donations. As of September + 30, we raised $328,482. Our 2018 fundraising goal + is $1,250,00 and we are continuing to work hard to + meet and exceed this goal! Please consider making + a donation to help us continue and increase our + support for FreeBSD: https://www.FreeBSDfoundation.org/donate/.

+ +

We also have a new Partnership Program, to provide more + benefits for our larger commercial donors. Find + out more information at https://www.FreeBSDfoundation.org/FreeBSD-foundation-partnership-program/ + and share with your companies!

+ +

OS Improvements

+ +

The Foundation improves the FreeBSD operating system by + employing technical staff to maintain and improve + critical kernel subsystems, add features and + functionality, and fix problems. This also + includes funding separate project grants like the + arm64 port, porting the blacklistd access control + daemon, and the integration of VIMAGE support, to + make sure that FreeBSD remains a viable solution + for research, education, computing, products and + more.

+ +

We kicked off or continued the following projects last + quarter:

+ +
    +
  • OpenZFS RAID-Z Expansion project
    • + +
  • Headless mode out-of-the-box for embedded ARM boards like + the Beaglebone Black
    • + +
  • Performance and scalability improvements
    • +
+ +

+ Having software developers on staff has allowed us to jump + in and work directly on projects to improve + FreeBSD such as:

+ +
    +
  • ZFS improvements
    • + +
  • New Intel server support
    • + +
  • kqueue(2) updates
    • + +
  • 64-bit inode support
    • + +
  • Stack guard
    • + +
  • Kernel Undefined Behavior Sanitizer
    • + +
  • Toolchain projects
    • + +
  • i915 driver investigation
    • + +
  • NVDIMM support in acpiconf(8)
    • + +
  • Continuous integration dashboard (web page and physical + hardware)
    • + +
  • FAT filesystem support in makefs(8)
    • +
+ +

+ Continuous Integration and Quality Assurance

+ +

The Foundation provides a full-time staff member who is + working on improving our automated testing, + continuous integration, and overall quality + assurance efforts.

+ +

Foundation employee Li-Wen Hsu set up new CI servers to + speed up amd64 build and test jobs, to reduce the + latency between changes being committed and + results being available. Li-Wen also set up a + staging / development server in order to test + changes to the CI system itself without affecting + production results. We have also started a small + hardware test lab, currently connected to the + staging server, that tests the full boot and test + cycle on physical hardware. In the near future + additional hardware devices will be added, and + this will migrate to the production CI server.

+ +

Release Engineering

+ +

The Foundation provides a full-time staff member to lead + the release engineering efforts. This has provided + timely and reliable releases over the last five + years.

+ +

Foundation employee Glen Barber continued leading the + efforts on the upcoming 12.0-RELEASE. For details + surrounding the work involved and progress thus + far on 12.0-RELEASE, please see the FreeBSD + Release Engineering Team section of this quarterly + status report.

+ +

Supporting FreeBSD Infrastructure

+ +

The Foundation provides hardware and support to improve + the FreeBSD infrastructure. Last quarter, we + continued supporting FreeBSD hardware located + around the world.

+ +

FreeBSD Advocacy and Education

+ +

A large part of our efforts are dedicated to advocating + for the Project. This includes promoting work + being done by others with FreeBSD; producing + advocacy literature to teach people about FreeBSD + and help make the path to starting using FreeBSD + or contributing to the Project easier; and + attending and getting other FreeBSD contributors + to volunteer to run FreeBSD events, staff FreeBSD + tables, and give FreeBSD presentations.

+ +

The FreeBSD Foundation sponsors many conferences, events, + and summits around the globe. These events can be + BSD-related, open source, or technology events + geared towards underrepresented groups. We support + the FreeBSD-focused events to help provide a venue + for sharing knowledge, to work together on + projects, and to facilitate collaboration between + developers and commercial users. This all helps + provide a healthy ecosystem. We support the + non-FreeBSD events to promote and raise awareness + of FreeBSD, to increase the use of FreeBSD in + different applications, and to recruit more + contributors to the Project.

+ +

Check out some of the advocacy and education work we did + last quarter:

+ +
    +
  • Organized and ran the Essen FreeBSD Hackathon in Essen, + Germany
    • + +
  • Participated in the FreeBSD Developer Summit BSDCam, in + Cambridge, England
    • + +
  • Represented FreeBSD at the ARM Partner Meeting
    • + +
  • Presented and taught about FreeBSD at SdNOG 5 in Khartoum, + Sudan
    • + +
  • Exhibited and gave a talk at OSCON 2018 in Portland, OR
    • + +
  • Exhibited at the 2018 Grace Hopper Celebration and + sponsored as a Silver Non-Profit Sponsor
    • + +
  • Exhibited at COCON 2018 in Taipei, Taiwan
    • + +
  • Sponsored and gave presentations and tutorials at + EuroBSDCon in Bucharest, Romania
    • + +
  • Organized and ran the Bucharest FreeBSD Developer Summit
    • + +
  • Sponsored the 2018 USENIX Security Symposium in Baltimore, + MD as an Industry Partner
    • + +
  • Provided FreeBSD advocacy material
    • + +
  • Sponsored the 2018 USENIX Annual Technical Conference in + Boston, MA as an Industry Partner
    • + +
  • Sponsored the OpenZFS Developer Summit as a Silver Sponsor
    • + +
  • Presented and taught about FreeBSD at SANOG32 in Dhaka, + Bangladesh
    • + +
  • Sponsored the SNIA Storage Developer Conference 2018 as an + Association Partner
    • + +
  • Provided 11 travel grants to FreeBSD contributors to + attend many of the above events.
    • +
+ +

+ We continued producing FreeBSD advocacy material to help + people promote FreeBSD around the world.

+ +

Read more about our conference adventures in the + conference recaps and trip reports in our monthly + newsletters: https://www.freebsdfoundation.org/news-and-events/newsletter/

+ +

We help educate the world about FreeBSD by publishing the + professionally produced FreeBSD Journal. Last + quarter we published the July/August issue that + you can find at https://www.FreeBSDfoundation.org/journal/.

+ +

You can find out more about events we attended and + upcoming events at https://www.FreeBSDfoundation.org/news-and-events/.

+ +

Legal/FreeBSD IP

+ +

The Foundation owns the FreeBSD trademarks, and it is our + responsibility to protect them. We also provide + legal support for the core team to investigate + questions that arise.

+ +

Go to http://www.FreeBSDfoundation.org + to find out how we support FreeBSD and how we can + help you!

+ + + + + + + Continuous Integration + + + + Jenkins Admin + jenkins-admin@FreeBSD.org + + + Li-Wen Hsu + lwhsu@FreeBSD.org + + + + + FreeBSD Jenkins Instance + FreeBSD CI artifact archive + FreeBSD Jenkins wiki + freebsd-testing Mailing List + freebsd-ci Repository + + + +

The FreeBSD CI team maintains continuous integration tasks + for FreeBSD. The CI + system regularly checks the changes committed to the + project's Subversion + repository can be successfully built, and performs various + tests and analysis + with the build results. The CI team also maintains the + archive of the artifact + built by the CI system, for the further testing and + debugging needs.

+ +

Starting from June 2018, the project is sponsored by the + FreeBSD Foundation in + hardware and staff. For more details of the sponsored + projects, please refer + to:

+ +

https://www.freebsdfoundation.org/news-and-events/newsletter/freebsd-foundation-update-september-2018/

+ +

In addition to that, we also helped checking regressions + for OpenSSL 1.1.1 + update and test continuously for 12-STABLE branch.

+ +

We had meetings and working groups at two developer + summits during 2018Q3:

+ + + +

+ Work in progress:

+ +
    +
  • Fixing the failing test cases and builds
    • + +
  • DTrace + test
    • + +
  • ZFS + test
    • + +
  • GCC + build
    • + +
  • Adding drm ports building test against -CURRENT
    • + +
  • Adding tests for selected project branches, e.g.: + clang700-import
    • + +
  • Adding new hardware to the embedded testbed
    • + +
  • Implementing automatic tests on bare metal hardware
    • + +
  • Planning running ztest and network stack tests
    • +
+ + + + + + + 4G/4G address space split for i386 + + + + Konstantin Belousov + kib@FreeBSD.org + + + + +

Most 32-bit FreeBSD architectures, including i386, started + to suffer + from the rapid growth of the size of software during the + past decade. + When a 32-bit address space is enough space for a given + task, 32-bit + mode still has an intrinsic advantage over 64-bit mode, + due to less + memory traffic and more economical use of caches. It has + grown + harder to provide the self-hosting i386 system build due + to the + increase in size of the build tools.

+ +

The FreeBSD i386 kernel, prior to the 12.0-RELEASE + version, split + the 4GB address space of the platform into 3GB (minus 4MB) + accessible + to userspace accesses and 1GB for kernel accesses. + Neither kernel nor userspace could access a full 4GB + address space. + Programs that require very large virtual address spaces, + such as + clang when compiling or lld when linking, could run out of + address + space: 3GB of address space was insufficient for their + operation. + The kernel also had trouble fitting into the traditional + 1GB + limitation of address space with the modern sizing for + network + buffers, ZFS and other KVA-hungry in-kernel subsystems.

+ +

In FreeBSD 12, the i386 architecture has been changed to + provide + dedicated separate address spaces for userspace and + kernel, giving + each mode full access to 4GB (minus 8MB) of usable address + space. + The userspace on the i386 architecture now has access to + the same + amount of address space as the compat32 subsystem in the + amd64 + architecture kernel. The increase in kernel address space + enables + further growth and maintainability of the i386 + architecture.

+ +

The split 4GB/4GB user/kernel implementation uses two page + directory + entries (PDEs) shared between modes: one for mapping the + page table, + another for the mode switching trampoline and other + required system *** DIFF OUTPUT TRUNCATED AT 1000 LINES ***