Small change to Package Contributor's Guide?

Small change to Package Contributor's Guide?

[Bob Heckel]

[-- Attachment #1: Type: text/plain, Size: 830 bytes --]

Hi,

To keep new or less active maintainers (such as myself) from accidentally
embarrassing themselves with post-upload announcement email subject
lines containing "[ANNOUNCEMENT][ANNOUNCEMENT]", is there any interest
in making this edit, or a variation of it, to setup.html?:

old:
----
  Once sent, your message will be reviewed by one of the cygwin-announce
  moderators and, once approved, will be automatically forwarded to the
  cygwin mailing list with an [ANNOUNCEMENT] prepended to the subject.

new:
----
  Once sent, your message will be reviewed by one of the cygwin-announce
  moderators and, once approved, will be automatically forwarded to the
  cygwin mailing list. Unlike other announcement subject lines that may
  start with "[RFU], [ITP]", etc. do not prepend this announcement with
  "[ANNOUNCEMENT]".


Bob

[-- Attachment #2: setup.html.patch --]
[-- Type: application/octet-stream, Size: 1393 bytes --]

--- setup.html	2012-10-12 15:23:03.939133900 -0400
+++ setup.new.html	2012-10-12 15:43:37.517258900 -0400
@@ -501,7 +501,7 @@
    Please do specify which version must be kept as "old", all the others will be deleted from the server.</li>
   <li>Feel free to delete your temporary copy once the files have been uploaded to sourceware.org. This fact will be made clear by an "Uploaded." reply to your announcement by someone with upload privileges.</li>
   <li>Announce via the <tt>cygwin-announce</tt> mailing list that the new package is available. Use the <a href="#announcement">announce message example</a> listed later in this page as a template for your announcement..<br />
-   Once sent, your message will be reviewed by one of the cygwin-announce moderators and, once approved, will be automatically forwarded to the cygwin mailing list with an [ANNOUNCEMENT] prepended to the subject.</li>
+   Once sent, your message will be reviewed by one of the cygwin-announce moderators and, once approved, will be automatically forwarded to the cygwin mailing list. Unlike other announcement subject lines that may start with "[RFU]", "[ITP]", etc.<i>do not</i> prepend this announcement with "[ANNOUNCEMENT]".</li>
 </ol>
 <p>NOTE: On any major version upgrade, you may want to mark the release as <tt>Test</tt>.</p>
 <h2><a id="announcement" name="announcement">Example announcement</a></h2>

Re: Small change to Package Contributor's Guide?

[Christopher Faylor]

On Sat, Oct 13, 2012 at 09:37:28AM -0400, Bob Heckel wrote:
>Hi,
>
>To keep new or less active maintainers (such as myself) from accidentally
>embarrassing themselves with post-upload announcement email subject
>lines containing "[ANNOUNCEMENT][ANNOUNCEMENT]", is there any interest
>in making this edit, or a variation of it, to setup.html?:
>
>old:
>----
>  Once sent, your message will be reviewed by one of the cygwin-announce
>  moderators and, once approved, will be automatically forwarded to the
>  cygwin mailing list with an [ANNOUNCEMENT] prepended to the subject.
>
>new:
>----
>  Once sent, your message will be reviewed by one of the cygwin-announce
>  moderators and, once approved, will be automatically forwarded to the
>  cygwin mailing list. Unlike other announcement subject lines that may
>  start with "[RFU], [ITP]", etc. do not prepend this announcement with
>  "[ANNOUNCEMENT]".

I don't see what was unclear about the old wording.  Your proposed wording
implies that announcement messages begin with [RFU] or [ITP] and that is
not accurate.  That's what shows up in cygwin-apps messages.

cygwin-apps != cygwin-announce

cgf

Re: Small change to Package Contributor's Guide?

[Bob Heckel]

On Sat, Oct 13, 2012 at 11:41 AM, Christopher Faylor  wrote:
> I don't see what was unclear about the old wording.  Your proposed wording
> implies that announcement messages begin with [RFU] or [ITP] and that is
> not accurate.  That's what shows up in cygwin-apps messages.
>
> cygwin-apps != cygwin-announce

Good point.   It's fine as is.