Re: Please *wait* before sending cygwin-announce messages
Christopher Faylor schrieb: I've noticed a new trend recently with package maintainers sending their cygwin-announce messages before they have been notified that the package has been uploaded. Please don't do that. Sorry, will not happen again. Please *do* send your upload announcements here, but just the raw facts, please, no descriptions of why you are updating or what the new features are. Just URLs are all that is required. IF the package has subdirectores and if you can duplicate the layout of the release directory where the package resides that would be useful too. It means that we can just use wget to download the package directly. When someone informs you that the package has been updated, *then* send an announcement to cygwin-announce. As always make sure that you include details about how to unsubscribe in your message. -- Reini
Re: Please *wait* before sending cygwin-announce messages
Just as a thought, could the announcement be a text file contained in the package? That could be extracted by upset(?) and sent when it detects the new version? This would have the benefits that 1) the GTG could check for its existance 2) the email would never be sent until the package was available 3) folks shouldn't forget to send the email (the only thing that they might forget to do is update it) 4) the text file could be appended with the unsubscribe information before it was sent. 5) the package script (sorry Igor can't remember what it's called atm) could either check for its existance or create a stub or... something automated ;) I know that it'd mean changing some programs/scripts (esp upset) but what do you think to the idea? J.
Re: Please *wait* before sending cygwin-announce messages
Christopher Faylor wrote: On Wed, Dec 07, 2005 at 05:10:06PM -0800, Harold L Hunt II wrote: Christopher Faylor wrote: Please *do* send your upload announcements here, but just the raw facts, [snip] Let me see if I am reading this correctly: When sending a message to cygwin-announce, "here" == cygwin-apps, not cygwin-announce. To summarize, the steps are: 1) send an upload announcement here (cygwin-apps) with just the bare facts required to get the packages onto sourceware. 2) someone says "Done", indicating that the packages have been uploaded. 3) you, having waited patiently here (cygwin-apps) for notice that your packages are now uploaded to sourceware.org then immediately send out an announcement to cygwin-announce (there). Said announcement should contain unsubscribe details. Ah ha, that's it (the here being cygwin-apps), thanks for the clarification. Harold
Re: Please *wait* before sending cygwin-announce messages
On Wed, Dec 07, 2005 at 05:10:06PM -0800, Harold L Hunt II wrote: >Christopher Faylor wrote: >>Please *do* send your upload announcements here, but just the raw facts, > >[snip] > >Let me see if I am reading this correctly: > >When sending a message to cygwin-announce, "here" == cygwin-apps, not cygwin-announce. To summarize, the steps are: 1) send an upload announcement here (cygwin-apps) with just the bare facts required to get the packages onto sourceware. 2) someone says "Done", indicating that the packages have been uploaded. 3) you, having waited patiently here (cygwin-apps) for notice that your packages are now uploaded to sourceware.org then immediately send out an announcement to cygwin-announce (there). Said announcement should contain unsubscribe details. cgf
Re: Please *wait* before sending cygwin-announce messages
Christopher Faylor wrote: [snip] Please *do* send your upload announcements here, but just the raw facts, please, no descriptions of why you are updating or what the new features are. Just URLs are all that is required. [snip] Let me see if I am reading this correctly: When sending a message to cygwin-announce, it should not contain any information about the motivation for the update (e.g. sync with upstream or Cygwin-specific bug fix), nor should it contain a list of features and/or bug fixes? When you say "just URLs are required", did you mean to say "if the information is available on the web (e.g. on an upstream project web page), just include a URL instead of copying and pasting"? I can agree with that, that would cut out a lot of information that is available elsewhere. But the lack of a description of the motivation for the update seems a little odd, that information is simply not available elsewhere. Did I misread the request? Harold
Please *wait* before sending cygwin-announce messages
I've noticed a new trend recently with package maintainers sending their cygwin-announce messages before they have been notified that the package has been uploaded. Please don't do that. Please *do* send your upload announcements here, but just the raw facts, please, no descriptions of why you are updating or what the new features are. Just URLs are all that is required. IF the package has subdirectores and if you can duplicate the layout of the release directory where the package resides that would be useful too. It means that we can just use wget to download the package directly. When someone informs you that the package has been updated, *then* send an announcement to cygwin-announce. As always make sure that you include details about how to unsubscribe in your message. cgf
