Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Baptiste Jonglez <baptiste@bitsofnetworks.org>
To: Stuart Cardall <developer@it-offshore.co.uk>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Release monitoring (Was: Wireguard added to Alpine Linux)
Date: Wed, 8 Mar 2017 17:05:29 +0100	[thread overview]
Message-ID: <20170308160529.GB21799@tuxmachine.polynome.dn42> (raw)
In-Reply-To: <02a8fddb-7246-984c-c51c-cd8fe3925694@it-offshore.co.uk>

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

Hi Stuart,

On Thu, Mar 02, 2017 at 09:49:53PM +0000, Stuart Cardall wrote:
> To monitor releases @ Alpine we use https://release-monitoring.org/ - if
> it doesn't pick up the changes I'll subscribe.

Thanks for mentioning this, it's a nice tool!  I started using it for
other projects.  By the way, receiving notification emails is non-obvious:
you have to register on https://apps.fedoraproject.org/notifications and
add a filter that matches the upstream projects you are interested in.

I just added wireguard [1], the monitoring system is configured to scrape
https://git.zx2c4.com/WireGuard/ and look for "WireGuard-([\d\.]*).tar.xz"
to extract a version number.

Baptiste

[1] https://release-monitoring.org/project/13481/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2017-03-08 16:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <6b590394-3134-b725-a063-0993b32a51c4@it-offshore.co.uk>
2017-03-02 15:33 ` Wireguard added to Alpine Linux Jason A. Donenfeld
2017-03-02 21:49   ` Stuart Cardall
2017-03-03  3:24     ` Jason A. Donenfeld
2017-03-23 19:39       ` Stuart Cardall
2017-03-08 16:05     ` Baptiste Jonglez [this message]
2017-03-08 17:12       ` Release monitoring (Was: Wireguard added to Alpine Linux) Stuart Cardall
2017-03-08 18:05       ` Stuart Cardall
2017-03-10  3:14         ` Jason A. Donenfeld

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=20170308160529.GB21799@tuxmachine.polynome.dn42 \
    --to=baptiste@bitsofnetworks.org \
    --cc=developer@it-offshore.co.uk \
    --cc=wireguard@lists.zx2c4.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 NNTP newsgroup(s).