QA's Package update policy proposal

[Bruno Wolff III]

On Tue, Mar 09, 2010 at 15:43:04 -0500,
  James Laska <jlaska at redhat.com> wrote:
> 
>      1. repoclosure/conflicts - no package update can introduce broken
>         deps or conflicts.  I'd recommend we apply this to both
>         'updates-testing' and 'updates' (but that's detailed below)
>      2. Package sanity
>               * No rpmlint failures
>               * Is the Source properly defined
>               * License review/examination (if possible)
>               * Upstream Source match tarball
>               * Package scriptlet syntax checks
>      3. Package must be newer than previously released versions - can't
>         ship newer package in N-1.
>      4. Any additional MUST requirements folks would like to see covered
>         from the package review requirements?

File conflicts (assuming that "conflicts" above referred to just conflicts
dependencies).