On Thu, 2009-02-19 at 11:20 -0500, Tom Lane wrote: > I think though that there might be a market for an intermediate-volume > list; or perhaps the restrictions on fedora-devel-announce are too > tight. The use-case I'm thinking of is "heads up" announcements that > someone is about to break compatibility of a given package. Currently > we do that on fedora-devel-list, and it's easy for someone to miss that > something is happening to a package they depend on. Somebody made a > suggestion a month or two back to move those announcements to > fedora-devel-announce (with any followup discussion on -devel). As far > as I've seen that's not been adopted, and the current guidelines for > -announce certainly don't seem to favor it. > > In short, -announce currently seems intended only for announcements that > just about every Fedora developer had better pay attention to. What > should we do with announcements that affect only customers of particular > packages? Hrm, can you point to guidelines for fedora-devel-announce that would make it seem that it isn't useful for such announcements? They really are infrequent and I would approve such postings from the moderator queue. I'm really not in favor of more lists. more lists just means more people not getting the information, or just tacking on more to: entries for every announcement causing splintered discussions, etc... If you know what packages are being effected by your bump, tack on <package>-owner@xxxxxxxxxxxxxxxxx to your to or cc list. That'll get into the inboxes (or wherever it is filtered) for the maintainers who concern themselves with the packages in question. -- Jesse Keating Fedora -- Freedom² is a feature! identi.ca: http://identi.ca/jkeating
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
