Add Glen Barber <gjb@FreeBSD.org>'s Release Engineering report.
This commit is contained in:
Warren Block
parent
8d7c3da5e2
commit
06881b3bb6
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=46959
1 changed files with 125 additions and 1 deletions
|
|
@ -156,7 +156,7 @@
|
||||||
have more news soon.</p>
|
have more news soon.</p>
|
||||||
|
|
||||||
<p>Methods of making it easier for people to contribute to
|
<p>Methods of making it easier for people to contribute to
|
||||||
documentation was another major topic. At present, we use
|
documentation was anoth er major topic. At present, we use
|
||||||
DocBook XML for articles and books, and mdoc(7) for man pages.
|
DocBook XML for articles and books, and mdoc(7) for man pages.
|
||||||
These markup languages are not very welcoming for new users.
|
These markup languages are not very welcoming for new users.
|
||||||
There are simpler documentation markup languages like RST,
|
There are simpler documentation markup languages like RST,
|
||||||
|
|
@ -530,4 +530,128 @@
|
||||||
Google Summer Of Code 2015
|
Google Summer Of Code 2015
|
||||||
</sponsor>
|
</sponsor>
|
||||||
</project>
|
</project>
|
||||||
|
|
||||||
|
<project cat='team'>
|
||||||
|
<title>&os; Release Engineering Team</title>
|
||||||
|
|
||||||
|
<contact>
|
||||||
|
<person>
|
||||||
|
<name>&os; Release Engineering Team</name>
|
||||||
|
<email>re@FreeBSD.org</email>
|
||||||
|
</person>
|
||||||
|
</contact>
|
||||||
|
|
||||||
|
<links>
|
||||||
|
<url href="https://www.freebsd.org/releases/10.2R/schedule.html">&os; 10.2-RELEASE schedule</url>
|
||||||
|
<url href="http://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/">&os; development snapshots</url>
|
||||||
|
<url href="https://lists.freebsd.org/pipermail/freebsd-snapshots/">&os; development snapshots announcements list</url>
|
||||||
|
</links>
|
||||||
|
|
||||||
|
<body>
|
||||||
|
<p>The &os; Release Engineering Team is responsible for setting
|
||||||
|
and publishing release schedules for official project releases
|
||||||
|
of &os;, announcing code freezes and maintaining the
|
||||||
|
respective branches, among other things.</p>
|
||||||
|
|
||||||
|
<p>The &os; 10.2-RELEASE cycle began in mid-June, with the
|
||||||
|
final release expected to be available in late August, and as
|
||||||
|
this quarterly status update shows, &os; 10.2-RELEASE is
|
||||||
|
going to be a very exciting release.</p>
|
||||||
|
|
||||||
|
<p>The &os; Release Engineering Team has been extremely busy
|
||||||
|
this quarter, with much of the focus targeted at adding
|
||||||
|
support for additional hardware and integration with
|
||||||
|
third-party hosting providers (aka "cloud"
|
||||||
|
hosting).</p>
|
||||||
|
|
||||||
|
<p>In follow-up with the work done by &a.andrew; to port &os; to
|
||||||
|
the ARM64 (aarch64) architecture, the Release Engineering
|
||||||
|
build tools were updated to produce &os;/aarch64 memory stick
|
||||||
|
images and virtual machine images for use with Qemu
|
||||||
|
(<tt>emulators/qemu-devel</tt>). At present, the Qemu virtual
|
||||||
|
machine images require an external EFI file to boot. Details
|
||||||
|
on how to boot &os;/aarch64 virtual machine images are
|
||||||
|
available in the &os; development snapshot announcement email
|
||||||
|
archives linked below.</p>
|
||||||
|
|
||||||
|
<p>Last quarter, several parts of the build tools were rewritten
|
||||||
|
to allow greater extensibility and granularity, which has
|
||||||
|
simplified the code required for new virtual machine
|
||||||
|
images.</p>
|
||||||
|
|
||||||
|
<p>In collaboration with several developers, the Release
|
||||||
|
Engineering build tools were updated to provide new support
|
||||||
|
for several hosting providers, as well as provide mechanisms
|
||||||
|
to automatically upload (and publish, where possible) &os;
|
||||||
|
virtual machine images.</p>
|
||||||
|
|
||||||
|
<p>This quarter, in addition to the existing support for the
|
||||||
|
Microsoft Azure platform, the build tools also natively
|
||||||
|
support:</p>
|
||||||
|
|
||||||
|
<ul>
|
||||||
|
<li>Amazon EC2 (thanks to &a.cperciva;)</li>
|
||||||
|
<li>Google Compute Engine (thanks to &a.swills;)</li>
|
||||||
|
<li>Vagrant/Hashicorp Atlas (thanks to &a.brd;)</li>
|
||||||
|
</ul>
|
||||||
|
|
||||||
|
<p>The &os; Release Engineering Team would like to thank these
|
||||||
|
developers for all of the work that went into making this
|
||||||
|
possible, and would like to especially thank &a.marcel; for
|
||||||
|
all of his work on the <tt>mkimg(1)</tt> utility, especially
|
||||||
|
for adding support for the various file formats requested.</p>
|
||||||
|
|
||||||
|
<p>In addition to the enhancements to the virtual machine build
|
||||||
|
tools, a significant amount of work went into refactoring the
|
||||||
|
build code used to produce &os;/arm images.</p>
|
||||||
|
|
||||||
|
<p>With much of the logic resembling how the <tt>Crochet</tt>
|
||||||
|
utility (written by &a.kientzle;) works, and a significant
|
||||||
|
amount of work, input, and advice from &a.ian;, &a.imp;,
|
||||||
|
&a.andrew;, &a.loos;, and a large number of contributors on
|
||||||
|
the <tt>freebsd-arm@FreeBSD.org</tt> mailing list, the &os;
|
||||||
|
Release Engineering tools now natively support producing
|
||||||
|
&os;/arm images without external build tools.</p>
|
||||||
|
|
||||||
|
<p>At present, the build tools are support building &os;/arm
|
||||||
|
images for:</p>
|
||||||
|
|
||||||
|
<ul>
|
||||||
|
<li><tt>BEAGLEBONE</tt></li>
|
||||||
|
<li><tt>CUBOX/HUMMINGBOARD</tt></li>
|
||||||
|
<li><tt>GUMSTIX</tt></li>
|
||||||
|
<li><tt>RPI-B</tt></li>
|
||||||
|
<li><tt>RPI2</tt> (&os;-CURRENT only)</li>
|
||||||
|
<li><tt>PANDABOARD</tt></li>
|
||||||
|
<li><tt>WANDBOARD</tt></li>
|
||||||
|
</ul>
|
||||||
|
|
||||||
|
<p>The &os; Release Engineering Team would like to thank each
|
||||||
|
of these people for their support and input, and would like to
|
||||||
|
especially thank &a.kientzle; for his work on
|
||||||
|
<tt>Crochet</tt>. Without it, we might not have been able to
|
||||||
|
produce images of the various boards that we are able to
|
||||||
|
now.</p>
|
||||||
|
|
||||||
|
<p>For more information on what else has changed in &os; since
|
||||||
|
10.1-RELEASE, see the
|
||||||
|
<a href="https://www.freebsd.org/relnotes/10-STABLE/relnotes/article.html">&os; 10.1-STABLE release notes</a>
|
||||||
|
(which will become the release notes for 10.2-RELEASE).</p>
|
||||||
|
|
||||||
|
<p>Additionally, &a.gjb; would like to thank Jim Thompson for
|
||||||
|
providing a BeagleBone Black board (replacing one that no
|
||||||
|
longer worked), and Benjamin Perrault for providing
|
||||||
|
a PandaBoard ES, both of which are used for locally testing
|
||||||
|
the images produced by the build tools.</p>
|
||||||
|
|
||||||
|
<p>Last, and certainly not least, &a.gjb; would also like to
|
||||||
|
thank the &os; Foundation for their support, and for
|
||||||
|
providing the resources (time and hardware) required to make
|
||||||
|
all of the items mentioned in this status report possible.</p>
|
||||||
|
</body>
|
||||||
|
|
||||||
|
<sponsor>
|
||||||
|
The &os; Foundation
|
||||||
|
</sponsor>
|
||||||
|
</project>
|
||||||
</report>
|
</report>
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue