count cleanup, and then mark as done since phk just committed the
expected changes. There might be more outstanding issues with this,
but the known ones are now covered.
information about the 'Developer Preview' snapshots (which will be
snapshots that have been polished by the RE team, with a full package
set, release documentation, etc..), the feature-list discussion we
will have to have at the FreeBSD Summit at Usenix, the feature freeze,
and then finally the code freeze.
is solely a schedule for 4.6.
* Link to the FAQ/#DEFINE-MFC at our first use of that acronym.
* Make a few 4.5 -> 4.6 changes that slipped through.
* Add an item for us to post the proposed package split for the
release media 2 weeks before the final release, to give stable users
the chance to scrutinize our selection of packages for the first CD.
about :
* Upcoming Release Schedule.
* Links to release engineering documentation.
* Specific schedule for FreeBSD 4.6.
* Current release engineering team.
In the very near future, this page will also contain a charter for the
RE team, a tentative schedule for 5.0, information about code freezes,
etc..
these entities may be used by other documents. Also, prepend "a." to
the developer entities, to clearly define the namespace used for this
purpose (as done in doc/).
are many native ABI calls with Giant still being set in syscalls.master.
Maxime Henrion is preparing patches that address this, and remove the
M* stuff in syscalls.master, so stick in his name as a co-conspirator.
but undefined: the de facto definition that appears to be in use, and
that I'm assuming still applies, is the following:
The "Responsible" field identifies a developer who has expressed
willingness to be responsible for completing the identified task;
this doesn't preclude others working on it, but suggests that
coordination with the responsible party might be appropriate so as
to avoid unnecessary duplication of work, and to maximize forward
progress.
Requested by: "Michael G. Petry" <petry@NetMasters.Com>
- Claim TrustedBSD locking. This isn't in the tree yet, but will begin
to migrate in in a month or so, and I am asserting to myself that it
will be locked when it arrives :-).
- Assign a variety of VFS locking-related tasks to Jeff Roberson. He
volunteered to work on these at BSDCon, so as a personal favor to him,
I'm making sure he can't forget. While I'm at it, add an entity for
him. The tasks he described include:
- Cleaning up locking within the vnode, including documenting
the various implicit and explicit locks there.
- Moving to explicit counting of soft references.
- Move towards using sx locks instead of lockmgr once this cleanup
is done.
- Moving towards being able to perform VOP_GETATTR() shared,
to reduce lock contention.
- Generally review vnode and VFS locking for SMP-safety.
Warner indicated at the developer summit that he'd be willing to give it
a shot, assign ownership to him for the time being. While I'm at it,
add an entity for Warner.
