Gentoo  Kernel  Team
                           Upgrade Policy

Background
----------
Gentoo Linux is more than a hobby, or a poject. To many people it is an integral
part of their business. Gentoo is well known for being a metadistribution, and
because of this much of its appeal is derived from portage. 
An absolute requirement when upgrading packages is to ensure the integrity of 
the portage tree once you have added your work.
This policy is set out to ensure that we do not accidentally break architectures
which are supported by our sources by lack of testing.

Update Procedure
----------------

1: Ensure the ebuild you are working on only has the architectures in KEYWORDS
   which you have verified. DO NOT carry these across from existing ebuilds.
2: Make sure that you only introduce new sources/patchsets into the testing
   profile, and not into stable. Only mark sources stable once they have proven
   themselves as such and have no gentoo specific bugs on bugzilla.
4: Check you have documented your changes from the previous version which
   are not part of the upstream changes.
5: Check that your newly updated ebuild doesnt orphan any other ebuilds in the
   package. If it does, remove the older ebuild from CVS.
6: Ensure all files are added to the tree, and you have run repoman scan.
7: Commit in the normal way.