Mike Noyes <[EMAIL PROTECTED]> writes: > > Right. And security advisories are a subcategory of "announcements", are > > they not? That's "announcements" as in "leaf-announce". > > Dan, > Security advisories are not a subset of announcements.
They are in most people's minds. That's why I wanted to clarify your statement. > They are > permitted on leaf-announce because we don't have a security list. Larger > projects usually have separate lists for security advisories and > announcements. Example: > http://www.debian.org/MailingLists/subscribe > debian-announce > debian-security-announce Sure, if you go up to the level of a whole OS, there will often be separate announce and security mailing lists, but 99+% of open source projects have a single <project>-announce list, which covers both general and security announcements. > > I suspect what you had in mind when you said "and/or" was that important > > stuff, including, but not limited to, security advisories, should go to > > leaf-announce, and less important stuff, like announcements of interesting > > potential LEAF hardware platforms, should be website posts. > > That is not what I had in mind. The person making the announcement needs > to decide the target audience. Our mailing lists reach a different set > of users than our web site. I think you're making the criteria more vague and complicated than need be. Bottom-line, stuff that's important for most or all LEAF users to hear, including, but not limited to, security advisories, should definitely be posted to leaf-announce. > > That just wasn't clear from your statement, > > I hope this message clarifies matters. Well, since you've redirected the thread off of leaf-user, it's partially a moot point. It wasn't clarification for me personally that I was driving for, but for others. But I suppose most of the people who are likely to have posts worthy of leaf-announce subscribe to leaf-devel. > BTW, regarding bugs: > Bugs are reported on leaf-user or in our SF project bug tracker. Then > corrected in cvs, and noted in a changlog of each release. You can > monitor all steps of this process if you want to. Okay. That conflicts with what Jacques said -- he said to use leaf-devel rather than leaf-user. But you both said to use the bug tracker, so as that's the most targeted path for bug reports, that's what I'll use in the future. You probably should update the Bering install and user's guides to say to use that, rather than saying to email you guys directly. -- Dan Harkless [EMAIL PROTECTED] http://harkless.org/dan/ ------------------------------------------------------- This sf.net email is sponsored by: Dice - The leading online job board for high-tech professionals. Search and apply for tech jobs today! http://seeker.dice.com/seeker.epl?rel_code=31 _______________________________________________ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
