It would get a bit confusing if others sent [UPDATE] or [UPDATES] messages since one expects to be able to use the "update from server" mechanism in Squeak to retrieve any [UPDATES]. So, yes, it would be good to "reserve" this for SC.
I think the primary message tags used in the Squeak list so far are: [BUG], [FIX], [ADDON], [GOODIE], [ANN], [ENH], and [UPDATES]; sometimes you will see [NEWBIE], [REQUEST] or [REQ], and [Q]. [ADDON] and [GOODIE] are pretty much equivalent - I prefer [GOODIE] for historical reasons. [ANN] is more general -- often applied to things like a new or updated port or VM or some such.
-- Dwight
Stephan Rudlof wrote:
Dear Dwight,
I thank you very much for your precise answers. I will post a summary to http://minnow.cc.gatech.edu/squeak.1, because I think its interesting for many others, too.
Just one remark:
All [UPDATE]s are issued by Squeak Central and announced on the list. The [UPDATE]s originate both from internal work done at SC and from selected [GOODIE]s, [ANN]s, [FIX]s, and [ENH]s sent to the list after SC has at least QCed them.
This means that nobody 'private' should sent an [UPDATE] message to this mailing list (but you can sent [GOODIE]s, [ANN]s, [FIX]s, and [ENH]s messages).
Stephan
I have made some docu at http://minnow.cc.gatech.edu/squeak.954 ..
Thank you Dwight and Dan!
Stephan
On Fri, 29 Oct 1999, Dwight Hughes wrote:
It would get a bit confusing if others sent [UPDATE] or [UPDATES] messages since one expects to be able to use the "update from server" mechanism in Squeak to retrieve any [UPDATES].
That was the initial intent of Dan's [UPDATE] prefix - to allow a mirror to fetch the updates asap. For example, I set up our mirror to check nightly for new updates, but the list is also grepped for an [UPDATE] without a "Re:" so the fetching starts immediately. Works fine (although the ftp-access seems to have gone so currently http-mirroring is used).
/bert
squeak-dev@lists.squeakfoundation.org