Maintainer Responsibility Policy
Nicolas Mailhot
nicolas.mailhot at laposte.net
Tue May 6 19:27:12 UTC 2008
Le lundi 05 mai 2008 à 22:22 -0400, Brian Pepple a écrit :
> On Mon, 2008-05-05 at 20:10 -0600, Kevin Fenzi wrote:
> > On Mon, 05 May 2008 21:01:35 -0400
> > bpepple at fedoraproject.org (Brian Pepple) wrote:
>
> > > === Maintain stability for users ===
> > > * Package maintainers should limit updates within a single
> > > Fedora release to those which do not require special user action. Many
> > > users update automatically, and if their applications stop
> > > working from no action of their own then they will be upset.
> > > This goes doubly for services which may break overnight.
> >
> > I would add additionally:
> >
> > "Maintainers should not push every single upstream update to all
> > branches. Examine the changes in each upstream release and ask if the
> > update is worth download and update time for many users. For upstreams
> > that update very often with many small updates, consider waiting and
> > updated only when the amount of changes is worth updating.
>
> Added.
***Except for fedora devel***
Maintainers that only update devel a few days before the freeze and
ignore intermediary versions (where problems in the package or in its
interaction with others could be identified and reported upstream) are
as time-wasting as maintainers who push everything everywhere.
Fedora devel has a limited number of users (except just before a
release). That does not mean ignoring it is ok for a maintainer.
--
Nicolas Mailhot
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: Ceci est une partie de message num?riquement sign?e
URL: <http://listman.redhat.com/archives/fedora-devel-list/attachments/20080506/5b8731cc/attachment.sig>
More information about the fedora-devel-list
mailing list