Portage bug handling
Important: This document is a draft and not in effect yet. Please don't link or refer to it yet unless you're discussing it.
Product and Components
All portage related bugs should be filed under the Portage Development
product. Bugs reassigned from other projects should get the product changed to
Version, Priority and Severity
The Version field should list the portage branch this bug will be fixed in.
This is aimed to target a specific branch in the subversion repository for possible fixes.
This field is generally not used for portage bugs yet.
||Any bugreports about adding/improving functionality
||grammer or layout errors in messages, wrong colors, aynthing where no brain work is involved and functionality isn't affected
||Typos, missing imports, indentation errors, other one-line fixes
||Bugs that require more than a one-line fix, but are easy to work around
||Bugs that prevent normal usage and require a lot of work
||Issues that break/corrupt package building on a large scale
||Critical data corruption or system breakage problems
Once a bug is supposed to be fixed in the subversion repository the InSVN
keyword is set, so fixed bugs are easy to find at release time.
Indicator for developers that this bug should be looked into soon, mainly used for enhancement bugs.
For problems that didn't appear in a previous version. This does not apply for
features that were intentionally dropped/changed.
The contents of this document, unless otherwise expressly stated, are licensed under the CC-BY-SA-2.5 license. The Gentoo Name and Logo Usage Guidelines apply.