public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Thomas Wolff <towo@towo.net>
To: cygwin-apps@cygwin.com
Subject: Re: Automatic announcement generation by calm
Date: Mon, 8 Jan 2024 14:01:46 +0100	[thread overview]
Message-ID: <5d19b39d-26e9-45a6-a003-6b9f403a306f@towo.net> (raw)
In-Reply-To: <ZZvr-4eOoOU_dqQV@calimero.vinschen.de>


Am 08/01/2024 um 13:35 schrieb Corinna Vinschen via Cygwin-apps:
> On Jan  7 16:12, Jon Turney via Cygwin-apps wrote:
>> This is an experimental facility, currently only available for packages
>> deployed from the build service [1] (that is, not for self-built packages
>> uploaded with 'cygport up' via sftp)
>>
>> When the token "announce" is present for a build job (in addition to
>> "deploy"), after a successful deploy, calm will automatically generate and
>> send an announce email.
>>
>> The mail follows a similar format to that generated by "cygport announce",
>> containing a list of packages and the description, with the following
>> addition:
>>
>> * If the cygport defines the variable "ANNOUNCE", it's evaluated contents
>> will be appended to the generated mail.
>>
>> * Otherwise, if the source package contains an ANNOUNCE file [2], it's
>> contents will be appended.
>>
>> * Otherwise, if the source package contains a README or ${PN}.README file,
>> lines that look like part of a changelog, between one starting with '----
>> ${PVR}' and the next starting '----', will be extracted and appended
>>
>> (None of these seem like a particularly great way of doing things, but they
>> match some historical patterns.  As always, suggestions about improvements
>> are welcome.)
>>
>>
>> In accordance with our long-standing policy of treating maintainer email
>> addresses as private information, the mail is sent from cygwin-no-reply and
>> bcc'ed to the uploader.
>>
>>
>> For testing purposes, if the token "mock" (yes, I am running out of synonyms
>> for "test"...) is also present, the mail will be only sent to the uploader,
>> not the announce list.
>>
>>
>> [1] https://cygwin.com/packaging/build.html
>> [2] Note that this isn't currently part of the default value of CYGWIN_FILES
>> [3], so needs to be explicitly listed there to be included in the source
>> package
>> [3] https://cygwin.github.io/cygport/src_prep_cygpart.html#CYGWIN_FILES
> :+1:
>
> Unfortunately I started the OpenSSH 9.6 build before reading this here,
> but that's some great addition.
>
> Corinna
I'd also appreciate to prefix the mail with an "[ANNOUNCEMENT] " tag as 
for the mails forwarded from cygwin-announcement to cygwin before that 
was stopped, to enhance the overview in users' mailboxes.
Thomas

  reply	other threads:[~2024-01-08 13:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-07 16:12 Jon Turney
2024-01-08 12:35 ` Corinna Vinschen
2024-01-08 13:01   ` Thomas Wolff [this message]
2024-01-08 13:42     ` Brian Inglis
2024-01-14 18:59       ` Jon Turney

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5d19b39d-26e9-45a6-a003-6b9f403a306f@towo.net \
    --to=towo@towo.net \
    --cc=cygwin-apps@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).