svn commit: r53102 - head/en_US.ISO8859-1/htdocs/news/status
Edward Tomasz Napierala
trasz at FreeBSD.org
Mon Jun 3 19:52:14 UTC 2019
Author: trasz
Date: Mon Jun 3 19:52:13 2019
New Revision: 53102
URL: https://svnweb.freebsd.org/changeset/doc/53102
Log:
Add Quarterly Status Report for 2019Q1.
Reviewed by: allanjude, bcr
Differential Revision: https://reviews.freebsd.org/D20446
Added:
head/en_US.ISO8859-1/htdocs/news/status/report-2019-01-2019-03.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 Jun 3 09:46:32 2019 (r53101)
+++ head/en_US.ISO8859-1/htdocs/news/status/Makefile Mon Jun 3 19:52:13 2019 (r53102)
@@ -82,6 +82,7 @@ XMLDOCS+= report-2017-07-2017-09
XMLDOCS+= report-2017-10-2017-12
XMLDOCS+= report-2018-01-2018-09
XMLDOCS+= report-2018-09-2018-12
+XMLDOCS+= report-2019-01-2019-03
XSLT.DEFAULT= report.xsl
Added: head/en_US.ISO8859-1/htdocs/news/status/report-2019-01-2019-03.xml
==============================================================================
--- /dev/null 00:00:00 1970 (empty, because file is newly added)
+++ head/en_US.ISO8859-1/htdocs/news/status/report-2019-01-2019-03.xml Mon Jun 3 19:52:13 2019 (r53102)
@@ -0,0 +1,2527 @@
+<?xml version="1.0" encoding="utf-8" ?>
+<!DOCTYPE report PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for
+ Status Report//EN"
+ "http://www.FreeBSD.org/XML/share/xml/statusreport.dtd" >
+
+<!-- $FreeBSD$ -->
+<!-- This file was generated with https://github.com/trasz/md2docbook -->
+<!--
+ Variables to replace:
+ %%START%% - report month start
+ %%STOP%% - report month end
+ %%YEAR%% - report year
+ %%NUM%% - report issue (first, second, third, fourth)
+ %%STARTNEXT%% - report month start
+ %%STOPNEXT%% - report month end
+ %%YEARNEXT%% - next report due year (if different than %%YEAR%%)
+ %%DUENEXT%% - next report due date (i.e., June 6)
+-->
+
+<report>
+ <date>
+ <month>January-March</month>
+
+ <year>2019</year>
+ </date>
+
+ <section>
+ <title>Introduction</title>
+
+ <p>As spring leads into summer, we reflect back on what the
+ FreeBSD project has accomplished in the first quarter of 2019.
+ Events included FOSDEM and AsiaBSDCon, the FreeBSD Journal
+ is now free to everyone, ASLR is available in -CURRENT and KPTI
+ can be controlled per-process. The run up to 11.3-RELEASE
+ has begun, and a team is applying syzkaller guided fuzzing
+ to the kernel, plus so much more. Catch up on many new and
+ ongoing efforts throughout the project, and find where you can
+ pitch in.</p>
+ </section>
+
+ <category>
+ <name>team</name>
+
+ <description>&os; Team Reports</description>
+
+ <p>Entries from the various official and semi-official teams,
+ as found in the <a href="&enbase;/administration.html">Administration
+ Page</a>.</p>
+ </category>
+
+ <category>
+ <name>proj</name>
+
+ <description>Projects</description>
+
+ <p>Projects that span multiple categories, from the kernel and userspace
+ to the Ports Collection or external projects.</p>
+ </category>
+
+ <category>
+ <name>kern</name>
+
+ <description>Kernel</description>
+
+ <p>Updates to kernel subsystems/features, driver support,
+ filesystems, and more.</p>
+ </category>
+
+ <category>
+ <name>arch</name>
+
+ <description>Architectures</description>
+
+ <p>Updating platform-specific features and bringing in support
+ for new hardware platforms.</p>.
+ </category>
+
+ <category>
+ <name>bin</name>
+
+ <description>Userland Programs</description>
+
+ <p>Changes affecting the base system and programs in it.</p>
+ </category>
+
+ <category>
+ <name>ports</name>
+
+ <description>Ports</description>
+
+ <p>Changes affecting the Ports Collection, whether sweeping
+ changes that touch most of the tree, or individual ports
+ themselves.</p>
+ </category>
+
+ <category>
+ <name>doc</name>
+
+ <description>Documentation</description>
+
+ <p>Noteworthy changes in the documentation tree or new external
+ books/documents.</p>
+ </category>
+
+ <category>
+ <name>misc</name>
+
+ <description>Miscellaneous</description>
+
+ <p>Objects that defy categorization.</p>
+ </category>
+
+ <category>
+ <name>third</name>
+
+ <description>Third-Party Projects</description>
+
+ <p>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.</p>
+ </category>
+
+ <project cat='team'>
+ <title>FreeBSD Release Engineering Team</title>
+
+ <contact>
+ <person>
+ <name>FreeBSD Release Engineering Team</name>
+ <email>re at FreeBSD.org</email>
+ </person>
+ </contact>
+
+ <links>
+ <url href="https://www.freebsd.org/releases/11.3R/schedule.html">FreeBSD 11.3-RELEASE schedule</url>
+ <url href="https://download.freebsd.org/ftp/snapshots/ISO-IMAGES/">FreeBSD development snapshots</url>
+ </links>
+
+ <body>
+ <p>The FreeBSD Release Engineering Team is responsible for
+ setting and
+ publishing release schedules for official project releases
+ of
+ FreeBSD, announcing code freezes and maintaining the
+ respective
+ branches, among other things.</p>
+
+ <p>During the first quarter of 2019, the FreeBSD Release
+ Engineering team
+ published the initial schedule for the upcoming the
+ 11.3-RELEASE.</p>
+
+ <p>FreeBSD 11.3-RELEASE will be the fourth release from the
+ <tt>stable/11</tt>
+ branch, building on the stability and reliability of
+ 11.2-RELEASE.
+ FreeBSD 11.3-RELEASE is currently targed for release in
+ early July, 2019.</p>
+
+ <p>Additionally throughout the quarter, several development
+ snapshots builds
+ were released for the <tt>head</tt>, <tt>stable/12</tt>,
+ and <tt>stable/11</tt> branches.</p>
+
+ <p>Much of this work was sponsored by the FreeBSD Foundation.</p>
+
+ </body>
+
+ </project>
+
+ <project cat='team'>
+ <title>Ports Collection</title>
+
+ <contact>
+ <person>
+ <name>René Ladan</name>
+ <email>portmgr-secretary at FreeBSD.org</email>
+ </person>
+ <person>
+ <name>FreeBSD Ports Management Team</name>
+ <email>portmgr at FreeBSD.org</email>
+ </person>
+ </contact>
+
+ <links>
+ <url href="https://www.FreeBSD.org/ports/">About FreeBSD Ports</url>
+ <url href="https://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html">Contributing to Ports</url>
+ <url href="http://portsmon.freebsd.org/index.html">FreeBSD Ports Monitoring</url>
+ <url href="https://www.freebsd.org/portmgr/index.html">Ports Management Team">Ports Management Team</url>
+ </links>
+
+ <body>
+ <p>As always, below is a summary of what happened in the
+ Ports Tree during the
+ last quarter.</p>
+
+ <p>During 2019q1, the number of ports dropped slightly to
+ just over 32,500. At
+ the end of the quarter, we had 2092 open port PRs. The
+ last quarter saw 8205
+ commits from 167 committers. So more PRs were closed and
+ more commits were
+ made than in 2018q4.</p>
+
+ <p>During the last quarter, we welcomed Kai Knoblich (kai@)
+ and said goodbye to
+ Matthew Rezny (rezny@).</p>
+
+ <p>On the infrastructure side, two new USES were introduced
+ (azurepy and sdl) and
+ USES=gecko was removed. The default versions of Lazarus
+ and LLVM were bumped
+ to 2.0.0 and 8.0 respectively. Some big port frameworks
+ that were end-of-life
+ were removed: PHP 5.6, Postgresql 9.3, Qt4, WebKit-Gtk and
+ XPI. Firefox was
+ updated to 66.0.2, Firefox-ESR to 60.6.1, and Chromium was
+ updated to
+ 72.0.3626.121.</p>
+
+ <p>During the last quarter, antoine@ ran 30 exp-runs for
+ package updates, moving
+ from GNU ld to LLVM ld, and switching clang to DWARF4.</p>
+
+ </body>
+
+ </project>
+
+ <project cat='team'>
+ <title>FreeBSD Core Team</title>
+
+ <contact>
+ <person>
+ <name>FreeBSD Core Team</name>
+ <email>core at FreeBSD.org</email>
+ </person>
+ </contact>
+
+ <body>
+ <p>The FreeBSD Core Team is the governing body of FreeBSD.</p>
+
+ <p>Core initiated a <tt>Release Engineering Charter
+ Modernization</tt> working
+ group. The purpose of the working group is to present (to
+ Core) a
+ modernized version of the <tt>Release Engineering
+ Charter</tt> and a first
+ version of a new <tt>Release Engineering Team Operations
+ Plan</tt>. The
+ group hopes to complete its goals and dissolve by
+ 2019-06-30.</p>
+
+ <p>The Core Team invites all members of the FreeBSD community
+ to
+ complete the <tt>2019 FreeBSD Community Survey</tt>.</p>
+
+ <p>https://www.research.net/r/freebsd2019</p>
+
+ <p>The purpose of the survey is to collect quantitative data
+ from the
+ public in order to help guide the project's priorities and
+ efforts.
+ It will remain open for 17 days and close at midnight May
+ 13 UTC
+ (Monday 5pm PDT).
+ (Editor's note: Survey has finished)</p>
+
+ <p>Core voted to approve source commit bits for Johannes
+ Lundberg
+ (johalun@) and Mitchell Horne (mhorne@) and associate
+ membership
+ for Philip Jocks. Core also voted to revoke Michael
+ Dexter's
+ documentation bit.</p>
+
+ <p>After a long lapse of not closing idle source commit bits,
+ core has
+ taken in the commit bit for these developers. We thank
+ each for
+ contributing to the project as a source committer.</p>
+
+ <ul>
+ <li>Alfred Perlstein (alfred@)</li>
+
+ <li>Eric Badger (badger@)</li>
+
+ <li>Daniel Eischen (deischen@)</li>
+
+ <li>Ermal Luçi (eri@)</li>
+
+ <li>Tony Finch (fanf@)</li>
+
+ <li>Justin T. Gibbs (gibbs@)</li>
+
+ <li>Imre Vadász (ivadasz@)</li>
+
+ <li>Julio Merino (jmmv@)</li>
+
+ <li>John W. De Boskey (jwd@)</li>
+
+ <li>Kai Wang (kaiw@)</li>
+
+ <li>Luigi Rizzo (luigi@)</li>
+
+ <li>Neel Natu (neel@)</li>
+
+ <li>Craig Rodrigues (rodrigc@)</li>
+
+ <li>Stanislav Sedov (stas@)</li>
+
+ <li>Thomas Quinot (thomas@)</li>
+
+ <li>Andrew Thompson (thompsa@)</li>
+
+ <li>Pyun YongHyeon (yongari@)</li>
+
+ <li>Zbigniew Bodek (zbb@)</li>
+ </ul>
+
+ <p></p>
+
+ </body>
+
+ </project>
+
+ <project cat='team'>
+ <title>FreeBSD Foundation</title>
+
+ <contact>
+ <person>
+ <name>Deb Goodkin</name>
+ <email>deb at FreeBSDFoundation.org</email>
+ </person>
+ </contact>
+
+ <body>
+ <p>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.</p>
+
+ <p>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.</p>
+
+ <p>Here are some highlights of what we did to help FreeBSD
+ last quarter:</p>
+
+ <p>We kicked off the year with an all-day board meeting in
+ Berkeley,
+ where FreeBSD began, to put together high-level plans for
+ 2019.
+ This included prioritizing technologies and features we
+ should support,
+ long-term planning for the next 2-5 years, and
+ philosophical discussions
+ on our purpose and goals.</p>
+
+ <p>Partnerships and Commercial User Support</p>
+
+ <p>We began the year by meeting with a few commercial users,
+ to help them
+ navigate working with the Project, and understanding how
+ they are using
+ FreeBSD. We're also in the process of setting up meetings
+ for Q2 and
+ throughout the rest of 2019. Because we're a 501(c)(3)
+ non-profit, we
+ don't directly support commercial users.
+ However, these meetings allow us to focus on facilitating
+ collaboration
+ with the community.</p>
+
+ <p>Fundraising Efforts</p>
+
+ <p>Our work is 100% funded by your donations. We kicked off
+ the year with many
+ individual and corporate donations, including donations
+ and commitments from
+ NetApp, Netflix, Intel, Tarsnap, Beckhoff Automation,
+ E-Card, VMware, and
+ Stormshield. We are working hard to get more commercial
+ users to give back
+ to help us continue our work supporting FreeBSD.
+ Please consider making a
+ <a
+ href="https://www.FreeBSDfoundation.org/donate/">donation</a>
+ to help us continue and increase our support for FreeBSD
+ at:
+ <a
+ href="https://www.FreeBSDfoundation.org/donate/">www.FreeBSDfoundation.org/donate/</a>.</p>
+
+ <p>We also have the 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!</p>
+
+ <p>OS Improvements</p>
+
+ <p>The Foundation improves the FreeBSD operating system by
+ employing our
+ 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.</p>
+
+ <p>Over the quarter there were 241 commits from nine
+ Foundation-sponsored staff
+ members and grant recipients.</p>
+
+ <p>We kicked off or continued the following projects last
+ quarter:</p>
+
+ <ul>
+ <li>FUSE file system kernel support (update and bug fixes)</li>
+
+ <li>Linuxulator testing and diagnostics improvements</li>
+
+ <li>SDIO and WiFi infrastructure improvements</li>
+
+ <li>x86-64 scalability and performance improvements</li>
+
+ <li>OpenZFS Online RAID-Z Expansion</li>
+ </ul>
+
+ <p>
+ Having software developers on staff has allowed us to jump
+ in and
+ work directly on projects to improve FreeBSD like:</p>
+
+ <ul>
+ <li>amd64 and i386 pmap improvements and bugfixes</li>
+
+ <li>address userland threading library issues</li>
+
+ <li>improve i386 support to keep the platform viable</li>
+
+ <li>improve FreeBSD on RISC-V</li>
+
+ <li>application of the Capsicum sandboxing framework</li>
+
+ <li>build system improvements and bug fixes</li>
+
+ <li>respond to reports of security issues</li>
+
+ <li>implement vulnerability mitigations</li>
+
+ <li>tool chain updates and improvements</li>
+
+ <li>adding kernel code coverage support for the
+ <a
+ href="https://github.com/google/syzkaller">Syzkaller</a>
+ coverage-guided system call
+ fuzzer</li>
+
+ <li>improved Syzkaller support for FreeBSD</li>
+
+ <li>improve the usability of <tt>freebsd-update</tt></li>
+
+ <li>improve network stack stability and address race
+ conditions</li>
+
+ <li>ensure FreeBSD provides userland interfaces required by
+ contemporary
+ applications</li>
+
+ <li>implement support for machine-dependent optimized
+ subroutines</li>
+
+ <li>update and correct documentation and manpages</li>
+
+ <li>DTrace bug fixes</li>
+
+ <li>update the FreeBSD Valgrind port and try to upstream the
+ changes</li>
+ </ul>
+
+ <p>
+ Continuous Integration and Quality Assurance</p>
+
+ <p>The Foundation provides a full-time staff member who is
+ working on improving
+ our automated testing, continuous integration, and overall
+ quality assurance
+ efforts.</p>
+
+ <p>During the first quarter of 2019, Foundation staff
+ continued improving the
+ project's CI infrastructure, working with contributors to
+ fix failing build
+ and test cases, and working with other teams in the
+ project for their
+ testing needs. In this quarter, we started publishing the
+ <a
+ href="https://lists.freebsd.org/mailman/listinfo/freebsd-testing">CI
+ weekly report</a>
+ on the freebsd-testing@ mailing list.</p>
+
+ <p>See the FreeBSD CI section of this report for more
+ information.</p>
+
+ <p>Release Engineering</p>
+
+ <p>The Foundation provides a full-time staff member to
+ oversee the
+ release engineering efforts. This has provided timely and
+ reliable releases
+ over the last five years.</p>
+
+ <p>During the first quarter of 2019, the FreeBSD Release
+ Engineering team
+ continued providing weekly development snapshots for
+ 13-CURRENT, 12-STABLE,
+ and 11-STABLE.</p>
+
+ <p>In addition, the Release Engineering team published the
+ schedule for the
+ upcoming 11.3-RELEASE cycle, the fourth release from the
+ stable/11 branch,
+ which builds on the stability and reliability of
+ 11.2-RELEASE.</p>
+
+ <p>The upcoming
+ <a
+ href="https://www.freebsd.org/releases/11.3R/schedule.html">11.3-RELEASE
+ schedule</a>
+ can be found at:
+ https://www.freebsd.org/releases/11.3R/schedule.html</p>
+
+ <p>FreeBSD 11.3 is currently targeted for final release in
+ early July 2019.</p>
+
+ <p>Please see the FreeBSD Release Engineering Team section of
+ this quarterly
+ status report for additional details surrounding the above
+ mentioned work.</p>
+
+ <p>Supporting FreeBSD Infrastructure</p>
+
+ <p>The Foundation provides hardware and support to improve
+ FreeBSD infrastructure. Last quarter, we continued
+ supporting FreeBSD hardware located
+ around the world.</p>
+
+ <p>FreeBSD Advocacy and Education</p>
+
+ <p>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.</p>
+
+ <p>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.</p>
+
+ <p>Check out some of the advocacy and education work we did
+ last quarter:</p>
+
+ <ul>
+ <li>Attended FOSDEM 2019 where we: staffed the FreeBSD Stand,
+ sponsored the
+ co-located FreeBSD Developer Summit, and gave the 25 Years
+ of FreeBSD
+ presentation in the BSD Dev room.</li>
+ </ul>
+
+ <p></p>
+
+ <ul>
+ <li>Sponsored and presented at SANOG33 in Thimphu, Bhutan</li>
+ </ul>
+
+ <p></p>
+
+ <ul>
+ <li>Represented FreeBSD at APRICOT 2019 in Yuseong-gu, Daejeon
+ South Korea</li>
+ </ul>
+
+ <p></p>
+
+ <ul>
+ <li>Sponsored the USENIX FAST conference in Boston, MA as an
+ Industry Partner</li>
+ </ul>
+
+ <p></p>
+
+ <ul>
+ <li>Ran our first ever FreeBSD track at
+ <a href="https://www.socallinuxexpo.org/scale/17x">SCALE
+ 17x</a>, which included an
+ all-day
+ <a
+ href="https://www.socallinuxexpo.org/scale/17x/presentations/getting-started-freebsd">Getting
+ Started with FreeBSD</a>
+ workshop. We were thrilled with the turnout of almost 30
+ participants and
+ received a lot of positive feedback. Thanks to Roller
+ Angel who taught the
+ class with the help of Deb Goodkin and Gordon Tetlow. We
+ also promoted
+ FreeBSD at the FreeBSD table in the Expo Hall.</li>
+ </ul>
+
+ <p></p>
+
+ <ul>
+ <li>Sponsored, presented, and exhibited at FOSSASIA in
+ Singapore</li>
+ </ul>
+
+ <p></p>
+
+ <ul>
+ <li>Sponsored AsiaBSDCon 2019</li>
+ </ul>
+
+ <p></p>
+
+ <ul>
+ <li>Committed to sponsoring Rootconf, BSDCan, and EuroBSDcon</li>
+ </ul>
+
+ <p></p>
+
+ <ul>
+ <li>Created registration systems for the Aberdeen Hackathon
+ and the upcoming
+ 2019 Vienna FreeBSD Security Hackathon</li>
+ </ul>
+
+ <p></p>
+
+ <ul>
+ <li>Provided FreeBSD advocacy material</li>
+ </ul>
+
+ <p></p>
+
+ <ul>
+ <li>Provided 3 travel grants to FreeBSD contributors to attend
+ many
+ of the above events.</li>
+ </ul>
+
+ <p>
+ We continued producing FreeBSD advocacy material to help
+ people promote
+ FreeBSD around the world.</p>
+
+ <p>Read more about our conference adventures in the
+ conference recaps and trip
+ reports in our
+ <a
+ href="https://www.freebsdfoundation.org/news-and-events/newsletter/">monthly
+ newsletters</a>.</p>
+
+ <p>We help educate the world about FreeBSD by publishing the
+ professionally produced FreeBSD Journal. We're excited to
+ announce that with
+ the release of the January/February 2019 issue, the
+ FreeBSD Journal is now a
+ free publication. Find out more and access the latest
+ issues at
+ <a
+ href="https://www.FreeBSDfoundation.org/journal/">www.FreeBSDfoundation.org/journal/</a>.</p>
+
+ <p>You can find out more about events we attended and
+ upcoming events at
+ <a
+ href="https://www.FreeBSDfoundation.org/news-and-events/">www.FreeBSDfoundation.org/news-and-events/</a>.</p>
+
+ <p>We also engaged with a new website developer to help us
+ improve our website
+ to make it easier for community members to find
+ information more easily and
+ to make the site more efficient.</p>
+
+ <p>Legal/FreeBSD IP</p>
+
+ <p>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.</p>
+
+ <p>Go to <a
+ href="http://www.FreeBSDfoundation.org">www.FreeBSDfoundation.org</a>
+ to find out
+ how we support FreeBSD and how we can help you!</p>
+
+ </body>
+
+ </project>
+
+ <project cat='team'>
+ <title>Continuous Integration</title>
+
+ <contact>
+ <person>
+ <name>Jenkins Admin</name>
+ <email>jenkins-admin at FreeBSD.org</email>
+ </person>
+ <person>
+ <name>Li-Wen Hsu</name>
+ <email>lwhsu at FreeBSD.org</email>
+ </person>
+ </contact>
+
+ <links>
+ <url href="https://ci.FreeBSD.org">FreeBSD Jenkins Instance</url>
+ <url href="https://artifact.ci.FreeBSD.org/">FreeBSD CI artifact archive</url>
+ <url href="https://wiki.freebsd.org/Jenkins">FreeBSD Jenkins wiki</url>
+ <url href="https://lists.FreeBSD.org/mailman/listinfo/freebsd-testing">freebsd-testing Mailing List</url>
+ <url href="https://github.com/freebsd/freebsd-ci">freebsd-ci Repository</url>
+ <url href="https://preview.tinyurl.com/y9maauwg">Tickets related to freebsd-testing@</url>
+ <url href="https://wiki.freebsd.org/HostedCI">Hosted CI wiki</url>
+ <url href="https://hackfoldr.org/freebsd-ci-report/">FreeBSD CI weekly report</url>
+ </links>
+
+ <body>
+ <p>The FreeBSD CI team maintains continuous integration
+ system and
+ related tasks for the FreeBSD project. The CI system
+ regularly
+ checks the changes committed to the project's Subversion
+ repository
+ can be successfully built, and performs various tests and
+ analysis
+ of the results. The results from build jobs are archived
+ in an
+ artifact server, for the further testing and debugging
+ needs. The
+ CI team members examine the failing builds and unstable
+ tests, and
+ work with the experts in that area to fix the code or
+ adjust test
+ infrastructure.</p>
+
+ <p>Starting from this quarter, we started to publish CI
+ weekly report at
+ <a
+ href="https://lists.freebsd.org/mailman/listinfo/freebsd-testing">freebsd-testing@</a>
+ mailing list. The archive is available at
+ <a
+ href="https://hackfoldr.org/freebsd-ci-report/">https://hackfoldr.org/freebsd-ci-report/</a></p>
+
+ <p>We also worked on extending test executing environment
+ to improve the code coverage, temporarily disabling flakey
+ test cases,
+ and opening tickets to work with domain experts. The
+ details are
+ of these efforts are available in the weekly CI reports.</p>
+
+ <p>We published the
+ <a
+ href="https://github.com/freebsd/fcp/blob/master/fcp-20190401-ci_policy.md">draft
+ FCP for CI policy</a>
+ and are ready to accept comments.</p>
+
+ <p>Please see freebsd-testing@ related tickets for more
+ information.</p>
+
+ <p>Work in progress:</p>
+
+ <ul>
+ <li>Fixing the failing test cases and builds</li>
+
+ <li>Adding drm ports building test against -CURRENT</li>
+
+ <li>Implementing automatic tests on bare metal hardware</li>
+
+ <li>Implementing the embedded testbed</li>
+
+ <li>Planning for running ztest and network stack tests</li>
+
+ <li>Help more 3rd software get CI on FreeBSD through a hosted
+ CI solution</li>
+ </ul>
+
+ <p></p>
+
+ </body>
+
+ </project>
+
+ <project cat='proj'>
+ <title>Security-Related changes</title>
+
+ <contact>
+ <person>
+ <name>Konstantin Belousov</name>
+ <email>kib at freebsd.org</email>
+ </person>
+ </contact>
+
+ <body>
+ <p>ASLR</p>
+
+ <p>The ASLR (Address Space Layout Randomization) patch from
+ <a href="https://reviews.freebsd.org/D5603">review
+ D5603</a> was
+ committed into svn. While debate continues about the
+ current and
+ forward-looking value ASLR provides, having an
+ implementation in
+ the FreeBSD source tree makes it easily available to those
+ who wish
+ to use it. This also moves the conversation past the
+ relative
+ merits to more comprehensive security controls.</p>
+
+ <p>KPTI per-process control</p>
+
+ <p>The KPTI (Kernel Page Table Isolation) implementation was
+ structured
+ so that most selections of page isolation mode were local
+ to the
+ current address space. In other words, the global control
+ variable
+ pti was almost unused in the code paths, instead the
+ user/kernel
+ %cr3 values were directly loaded into registers or
+ compared to see
+ if the user page table was trimmed. Some missed bits of
+ code were
+ provided by Isilon, and then bugs were fixed and last
+ places of
+ direct use of pti were removed.</p>
+
+ <p>Now when the system starts in the pti-enabled mode,
+ proccontrol(1) can
+ be used by root to selectively disable KPTI mode for
+ children of a
+ process. The motivation is that if you trust the program
+ that you
+ run, you can get the speed of non-pti syscalls back, but
+ still run
+ your normal user session in PTI mode. E.g., firefox would
+ be properly
+ isolated.</p>
+
+ <p>Feature-control bits</p>
+
+ <p>Every FreeBSD executable now contains a bit mask intended
+ for
+ enabling/disabling security-related features which makes
+ sense for the
+ binary. This mask is part of the executable segments
+ loaded on image
+ activation, and thus is part of any reasonable way to
+ authenticate the
+ binary content.</p>
+
+ <p>For instance, the ASLR compatibility is de-facto the
+ property of the
+ image and not of the process executing the image. The
+ first (zero)
+ bit in the mask controls ASLR opt-out. Other OSes (e.g.
+ Solaris) used
+ an OS-specific dynamic flag, which has the same runtime
+ properties
+ but leaves less bits to consume in the feature-control
+ mask.</p>
+
+ <p>The feature-control mask is read both by kernel and by
+ rtld during
+ image activation. It is expected that more features will
+ be added
+ to FreeBSD and the mask can be used for enabling/disabling
+ those
+ features..</p>
+
+ <p>It is expected that a tool to manipulate the mask will be
+ provided
+ shortly, see <a
+ href="https://reviews.freebsd.org/D19290">review
+ D19290</a>.</p>
+
+ <p></p>
+
+ </body>
+
+ <sponsor>
+ The FreeBSD Foundation
+ </sponsor>
+
+ </project>
+
+ <project cat='proj'>
+ <title>AXP803 PMIC driver update</title>
+
+ <contact>
+ <person>
+ <name>Ganbold Tsagaankhuu</name>
+ <email>ganbold at FreeBSD.org</email>
+ </person>
+ </contact>
+
+ <body>
+ <p>The AXP803 is a highly integrated PMIC that targets
+ Li-battery
+ (Li-ion or Li-polymer) applications. It provides flexible
+ power
+ management solution for processors such as the Allwinner
+ A64 SoC.
+ This SoC is used by <a
+ href="https://www.pine64.org/pinebook/">Pinebook</a>.</p>
+
+ <p>The following updates were performed on the AXP803 driver:</p>
+
+ <ul>
+ <li>Enabled necessary bits when activating interrupts. This
+ allows
+ reading some events from the interrupt status registers.
+ These
+ events are reported to devd via system "PMU" and subsystem
+ "Battery", "AC" and "USB" such as plugged/unplugged,
+ battery
+ absent, charged and charging.</li>
+
+ <li>Added sensors support for AXP803/AXP813. Sensor values
+ such as
+ battery charging, charge state, voltage, charging current,
+ discharging current, battery capacity can be obtained via
+ sysctl.</li>
+
+ <li>Added sysctl for setting battery charging current. The
+ charging
+ current can be set using steps from 0 to 13. These steps
+ correspond to 200mA to 2800mA, with a granularity of
+ 200mA/step.</li>
+ </ul>
+
+ <p></p>
+
+ </body>
*** DIFF OUTPUT TRUNCATED AT 1000 LINES ***
More information about the svn-doc-all
mailing list