[Sorry for the delayed reply -- these kind of delays in being able to catch up with leaf-devel and leaf-user are why I need to be able to depend on leaf-announce.]
guitarlynn <[EMAIL PROTECTED]> writes: > > Thus this is > > certainly something that should have been posted to leaf-announce, > > rather than crossposted to leaf-devel and leaf-user. Remember that > > there are people who only have time to follow leaf-announce. > > Dan, I believe that this statement is another thread that is being > discussed. If any discussion has been missed, they are available > through the mailing-list archives. We really don't need multiple threads > to discuss the same underlying point. I wasn't discussing the point in general, just making the point why this particular post should have been made to leaf-announce. > In fact, I believe you have made your opinion incrediably clear on the > subject of leaf-announce subject scope. If I made my point so clearly, I shouldn't have to remind you that it was my feeling that people are failing to use leaf-announce because they forget about it, not because they have philosophical reasons not to, and that people occasionally need to be reminded to use it. Indeed this is proven by the fact that Jacques agreed with me that leaf-announce should be used for this sort of thing, and then a couple days later forgot to use it again. > It was also made clear that no changes would be made > to the present system w/o the consensus of the developers. I'm not asking for any changes to be made to the present system. As Mike Noyes eventually made clear in his posts in that thread, the present "charter" for leaf-announce is not in conflict with my opinion as to its appropriate usage. > I understand and appreciate your opinion, however needlessly > making the same statement repeatably isn't going to influence > my feelings on the subject. The post was mainly intended for Jacques, not for you. > My opinion is that a bug/security > alert should be made in the proper place (bug-tracker) and > an alert to users should be made where the most users will be > notified (leaf-user). Any code changes necessary to fixing the > bug open for discussion should be done in the proper place as > well (leaf-devel). leaf-announce should be used for the intended > purpose.... announcement of new images and packages. In this case, Jacques was posting instructions on fixing errata in the current release of Bering because 1.0-rc4 is not immediately forthcoming. The same people who would be interested in an announcement of rc4 and its bugfixes would be interested in how to manually fix them in rc3, if rc4 won't be released for a while. -- 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
