os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Add core@ team report.

Browse source 
Submitted by:	core-secretary (matthew)
Sponsored by:	The FreeBSD Foundation
This commit is contained in:
Glen Barber 2014-07-13 23:17:31 +00:00
parent f89ae1cfba
commit adfaab115a
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=45277
1 changed files with 64 additions and 1 deletions

65
en_US.ISO8859-1/htdocs/news/status/report-2014-04-2014-06.xml
View file

@ -43,7 +43,7 @@
?> ?>
<p>Thanks to all the reporters for the excellent work! This <p>Thanks to all the reporters for the excellent work! This
report contains 7 entries and we hope you enjoy reading it.</p> report contains 8 entries and we hope you enjoy reading it.</p>
<p>The deadline for submissions covering between July and <p>The deadline for submissions covering between July and
September 2014 is October 7th, 2014.</p> September 2014 is October 7th, 2014.</p>
@ -575,4 +575,67 @@
<task>Support secure boot.</task> <task>Support secure boot.</task>
</help> </help>
</project> </project>
<project cat='team'>
<title>The &os; Core Team</title>
<contact>
<person>
<name>&os; Core Team</name>
<email>core@FreeBSD.org</email>
</person>
</contact>
<body>
<p>The &os; Core Team constitutes the project's "Board of
Directors", responsible for deciding the project's overall
goals and direction as well as managing specific areas of the
&os; project landscape.</p>
<p>Topics for core this quarter have included some far-reaching
policy reviews and some significant changes to the project
development methodology.</p>
<p>In May, a new release policy was published as well as being
presented at the BSDCan developer conference by John Baldwin.
The idea is that each major release branch (eg. 10.x) is
guarranteed to be supported for at least five years, but
individual point releases on each branch (eg. 10.0-RELEASE)
will be issued at regular intervals and only the latest point
release will be supported.</p>
<p>Another significant change did not receive approval. When
the change to the Bylaws reforming the core team election
process was put to the vote of all &os; developers it failed
to reach a quorum.</p>
<p>June saw the culmination of a long running project to replace
the project's bug tracking system. As of 3rd June the &os;
project has switched to Bugzilla as its bug tracking system.
All of the history of Gnats PRs has been preserved, so there
is no need to re-open old tickets. Work is still going on to
replicate some of the integration tweaks that had been applied
to Gnats, but all necessary functionality has been implemented
and the project is already seeing the benefits of the new
capabilities bought by Bugzilla.</p>
<p>An election to select core members for the next two year term
of office took place during this period. We would like to
thank retiring members of core for their years of service.
The new core team provides continuity with previous core
teams: about half are incumbents from the previous team, and
several former core team members have returned after a hiatus.
core now includes two members of the &os; Foundation board and
one other Foundation staff member, aiding greater coordination
at the top level of the project. At the same time the
core-secretary role was passed on to a new volunteer.</p>
<p>Other activities included providing consultation on licensing
terms for software within the &os; source tree, and oversight
of changes to the membership of postmaster and clusteradm.</p>
<p>Three new src commit bits were issued during this quarter,
and one was taken into safekeeping.</p>
</body>
</project>
</report> </report>