From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: New Release Schedule
Date: Mon, 12 Jun 2017 17:57:58 +0100 [thread overview]
Message-ID: <1497286678.21214.24.camel@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 378 bytes --]
Hello,
for everyone who did not attend the last telephone conference where the new
release schedule for Core Updates was presented, I wrote this all together here:
http://wiki.ipfire.org/devel/release-schedule
Since the new Core Update is imminent, the merge window for 112 closes today.
If there are any questions regarding this, please ask.
Best,
-Michael
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
reply other threads:[~2017-06-12 16:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1497286678.21214.24.camel@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.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