public inbox for ipfire-announce@lists.ipfire.org
 help / color / mirror / Atom feed
From: The IPFire Project <ipfire-announce@lists.ipfire.org>
To: ipfire-announce@lists.ipfire.org
Subject: IPFire 2.13 BETA releases
Date: Tue, 22 Jan 2013 17:47:08 +0100	[thread overview]
Message-ID: <mailman.223.1358873251.4626.ipfire-announce@lists.ipfire.org> (raw)

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

Hello,

this is a summary about the progress, we have made in getting IPFire
2.13 ready for release.

At the very beginning of the year, we released the first beta version,
which was followed by the second beta version, which was released
yesterday.

  IPFire 2.13 beta 1
  http://downloads.ipfire.org/release/55

  IPFire 2.13 beta 2
  http://downloads.ipfire.org/release/56
  

Overall, things calmed down and we did not experience any bigger
problems - although there have been some little beans that already have
been fixed. As IPFire 2.13 is already that stable, we would love if a
lot of you upgrade to the latest development version and help us finding
bugs.

  Learn how to upgrade:
  http://wiki.ipfire.org/en/configuration/ipfire/pakfire/testing


The amount of changes that have been done in IPFire 2.13 is very huge,
that we decided to break the change log into several parts. Please have
a look at them and stay tuned for the ones that are coming!

  IPFire 2.13 Beta 1 - Part 1 ARM
  http://planet.ipfire.org/post/ipfire-2-13-beta-1-part-1-arm

  IPFire 2.13 Beta 1 - Part 2 Strongswan 5 - IPsec VPN
  http://planet.ipfire.org/post/ipfire-2-13-beta-1-part-2-strongswan-5-ipsec-vpn

  IPFire 2.13 Beta 2 - Part 3 Wireless LAN
  http://planet.ipfire.org/post/ipfire-2-13-beta-2-part-3-wireless-lan


Thanks for reading this and we are happy if you decide to support us!


                 reply	other threads:[~2013-01-22 16:47 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.223.1358873251.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