From: Baptiste Jonglez <baptiste@bitsofnetworks.org>
To: "Jason A. Donenfeld" <zx2c4@gentoo.org>
Cc: zorun@bitsofnetworks.org, Christian Hesse <mail@eworm.de>,
WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [WireGuard] The Distro Package Maintainers Thread
Date: Mon, 11 Jul 2016 23:20:44 +0200 [thread overview]
Message-ID: <20160711212044.GA15134@lud.polynome.dn42> (raw)
In-Reply-To: <CAHmME9qvbXDENXbTYhcf58FR+1vGQfpABXKNRk04+GFM7dt0YA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 511 bytes --]
On Mon, Jul 11, 2016 at 07:51:12PM +0200, Jason A. Donenfeld wrote:
> Quick question -- how often is too often for you guys for publishing
> snapshots? Once a week okay? Twice a week okay? Twice a month okay? It
> doesn't matter because package bumping is all automated anyway?
As I said before, once every ~two weeks is the minimum for me, as I like
to at least compile-test a new release before publishing it...
You can release more often, but then I would probably skip releases
(which is not a big deal).
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-07-11 21:20 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-30 12:52 Jason A. Donenfeld
2016-06-30 13:28 ` Christian Hesse
2016-06-30 14:45 ` Bruno Wolff III
2016-06-30 15:03 ` Daniel Kahn Gillmor
2016-07-01 16:40 ` [WireGuard] debian packaging [was: Re: The Distro Package Maintainers Thread] Daniel Kahn Gillmor
2016-07-01 21:05 ` Jason A. Donenfeld
2016-07-01 21:11 ` Jason A. Donenfeld
2016-07-02 12:38 ` Daniel Kahn Gillmor
2016-07-06 22:34 ` Jason A. Donenfeld
2016-07-08 21:20 ` Daniel Kahn Gillmor
2016-06-30 15:30 ` [WireGuard] The Distro Package Maintainers Thread Baptiste Jonglez
2016-06-30 18:32 ` Jason A. Donenfeld
2016-06-30 18:42 ` Jason A. Donenfeld
2016-06-30 19:27 ` Christian Hesse
2016-06-30 19:34 ` Jason A. Donenfeld
2016-07-01 2:41 ` Jason A. Donenfeld
2016-07-01 12:26 ` Daniel Kahn Gillmor
2016-07-01 21:28 ` Jason A. Donenfeld
2016-07-01 21:45 ` Christian Hesse
2016-07-02 12:39 ` Daniel Kahn Gillmor
2016-07-02 15:55 ` Daniel Kahn Gillmor
2016-07-04 15:50 ` Jason A. Donenfeld
2016-07-04 22:57 ` Phillip Smith
2016-07-04 23:46 ` Jason A. Donenfeld
2016-07-05 1:15 ` Phillip Smith
2016-07-05 1:23 ` Jason A. Donenfeld
2016-07-05 19:05 ` Christian Hesse
2016-07-11 17:51 ` Jason A. Donenfeld
2016-07-11 21:20 ` Baptiste Jonglez [this message]
2016-07-11 22:34 ` Jason A. Donenfeld
2016-07-12 10:59 ` Daniel Kahn Gillmor
2016-07-12 15:27 ` Jason A. Donenfeld
2016-07-13 14:29 ` Jason A. Donenfeld
2016-07-13 16:35 ` Jason A. Donenfeld
[not found] ` <CAHmME9qQ=46ZyPLPAw8sDb1bhwWGdEcxoFpof3meV+WUKHrMfg@mail.gmail.com>
2016-07-13 16:42 ` Jason A. Donenfeld
2016-07-13 16:49 ` Baptiste Jonglez
2016-07-13 17:58 ` Jason A. Donenfeld
2016-07-13 18:15 ` Martin Hauke
2016-07-13 21:57 ` Daniel Kahn Gillmor
2016-07-14 14:27 ` Jason A. Donenfeld
2016-07-14 14:30 ` 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=20160711212044.GA15134@lud.polynome.dn42 \
--to=baptiste@bitsofnetworks.org \
--cc=mail@eworm.de \
--cc=wireguard@lists.zx2c4.com \
--cc=zorun@bitsofnetworks.org \
--cc=zx2c4@gentoo.org \
/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).