On Mon, 2008-05-05 at 21:25 -0400, Jesse Keating wrote: > On Mon, 2008-05-05 at 21:01 -0400, Brian Pepple wrote: > > == Maintainer Responsibility Policy == > > === How long to maintain? === > > 13 months from initial release. > > From initial Fedora release right? If you bring a package in around F10 > Beta, you're expected to stick around for 13 months after F10 final goes > out. Correct. I'll clarify that. > > > === Belong to the appropriate low-traffic mailing list === > > * Package maintainers will receive important announcements through > > the moderated fedora-devel-announce mailing list. Maintainers > > will be automatically subscribed to this list. > > Do we have this hooked up now, or is that a future item (the > autosubscribing) I thought that was already hooked up, but I could be mistaken on that point. Is anyone aware of the status of this? > > > > === Deal with reported bugs in a timely manner ==== > > * 'Nuff said. > > I would note here that putting a comment in the bug letting folks know > when you're going to be too busy to look at the bug immediately would > help. Agreed. I'll add it. > > === Notify others of changes that may affect their packages === > > * Some packages are depended upon by others; in this case, changes > > to one package may cause issues for others. Maintainers should > > be aware of the effects that changes to their packages may have, > > and should alert to the fedora-devel-announce mailing list of > > updates which contain ABI or API changes which may cause > > dependency problems for other packages. The announcement should > > occur a week before the packages update, so all maintainers > > affected are notified. The announcement should include the > > following information: > > * Nature of the change. > > * Branches (devel, F9, etc.) which will be affected by the > > change. > > * Expected date of the change. > > * List of packages which are affected by the change. > > Generally, this is merely the list of packages which > > depend directly on the package which is being updated, > > and can be found with "repoquery --whatrequires package" > > where "package" is the package being updated. > > Shouldn't there be an --all there, as well as looking at what packages > BuildRequire yours? Yeah, I think your right. Thanks for the feedback, Jesse. Later, /B -- Brian Pepple <bpepple@xxxxxxxxxxxxxxxxx> http://fedoraproject.org/wiki/BrianPepple gpg --keyserver pgp.mit.edu --recv-keys 810CC15E BD5E 6F9E 8688 E668 8F5B CBDE 326A E936 810C C15E
Attachment:
signature.asc
Description: This is a digitally signed message part
-- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
