From: The IPFire Project <ipfire-announce@lists.ipfire.org>
To: ipfire-announce@lists.ipfire.org
Subject: IPFire 2.13 - Core 66 released [FINAL]
Date: Tue, 19 Feb 2013 13:04:53 +0100 [thread overview]
Message-ID: <mailman.288.1361275538.4626.ipfire-announce@lists.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 655 bytes --]
Dear Community,
Today is the day on which we officially release IPFire 2.13. We are very
proud to have a brand new milestone release with a lot of exciting, new
features. We’d like to thank everyone who has contributed to the project
and if you would like to help us out as well, please consider making a
donation (http://www.ipfire.org/donate).
Because the announcement is very long and contains a lot of links we
would like to point you to the official text:
http://www.ipfire.org/news/ipfire-2-13-core-66-released
A German version is also available:
http://www.ipfire.org/news/ipfire-2-13-core-66-freigegeben
-Your IPFire Development Team
reply other threads:[~2013-02-19 12:04 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=mailman.288.1361275538.4626.ipfire-announce@lists.ipfire.org \
--to=ipfire-announce@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