Announcement: improved fedora.us UPDATE submission policy

[Ville Skyttä]

On Thu, 2004-06-24 at 14:15, Aurelien Bompard wrote:

> If the update requires a new package not yet published in Fedora.us, I guess
> we must still wait for this new package's approval, right ?

Yes.  If the new one (or whatever that is not in the repo) is a build
dependency, the package requiring it cannot obviously be built, so it
cannot enter the PENDING state.  PUBLISH may be ok; that depends.  An
example: https://bugzilla.fedora.us/show_bug.cgi?id=1512

If the new one is a run/install time dependency, the update can (but not
necessarily will) be built before the dep.  But it will be kept in
PENDING state and won't be released until the dependency is satisfied
within the published destination repo.

> What if a package is split in two during an update ? Should both packages be
> submitted it the PUBLISH status, or just the original one ? This is the
> case with the new version of psi :
> https://bugzilla.fedora.us/show_bug.cgi?id=1736

Apply common sense, that's what the "downgrading rights" comment is in
the policy for (below the diagram; I expanded the example a bit).  If
you are in doubt and/or want comments, submit with QA status.  If you're
completely sure that it's The Right Thing to do, submit with PUBLISH. 
Release managers do skim through comments for each submission though, so
there is always at least some level of casual checking involved.