[altq 297] altq merged into kame

[Kenjiro Cho <kjc@csl.sony.co.jp>]

Starting from January, I joined the KAME IPv6 development team, and
have already merged altq-2.1 into KAME.

KAME IPv6 will be a standard IPv6 codebase for all BSDs.  Efforts are
under way to merge the basic part of IPv6 into all BSD parties.
On the other hand, KAME will keep their own development tree that
includes advanced features under development such as IPSEC, multicast,
and ALTQ.
See http://www.kame.net/ for more info about KAME.

I'm going to move my ALTQ development environment to KAME.
This means that new features and bug fixes will be committed to the
KAME tree first.  Future ALTQ releases will be made out of the KAME 
tree.

This will reduce my release engineering work:
 - ALTQ now has 4 platforms (FreeBSD-2.x, FreeBSD-3.x, NetBSD and
   OpenBSD) and it has become too time consuming to test the code on 
   all the BSDs.
 - minor compilation errors or install problems will be easily noticed 
   and fixed by other KAME developers.
 - KAME has a much better system to support users:
	- cvsup, anoncvs to retrieve the latest tree
	- weekly snapshot, bi-monthly stable releases
	- cvsweb and problem report data base

There are benefits for ALTQ users:
 - bug fixes and new features become immediately available from
   cvsup (or anoncvs) or weekly-snapshots from KAME.
 - you can track down the commit history from the cvsweb at the KAME
   site.
 - it comes with IPv6 and other advanced features.

I'll report to this mailing list about future major changes in ALTQ.

I also encourage ALTQ users (especially, research people) to use KAME
for the above reasons, and to share problems or difficulties with
others on this list.

-Kenjiro