From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: IPFire 2.13 - Core Update 68 roadmap
Date: Sat, 11 May 2013 11:34:56 +0200 [thread overview]
Message-ID: <1368264896.1869.92.camel@rice-oxley.tremer.info> (raw)
In-Reply-To: <1368019198.1869.22.camel@rice-oxley.tremer.info>
[-- Attachment #1: Type: text/plain, Size: 2031 bytes --]
Since there is again less feedback than what we need to go on with this
update, I am going to revert the update accelerator stuff so that we can
release this update earlier.
-Michael
On Wed, 2013-05-08 at 15:19 +0200, Michael Tremer wrote:
> Hey,
>
> since we are already a bit behind the usual schedule, I am writing this
> email to briefly sum up what we are going to do:
>
> The update is already pretty big and comes with all sorts of fixes,
> enhancements and improvements. As there are two security-related issues
> I want to ship this as soon as possible.
>
> The only things missing are as follows:
> * Arne wants to update the usual databases (GeoIP, PCI IDs, USB IDs,
> etc.) what will be done very shortly before the release.
> * The GET fix for the new Update Accelerator GUI I am still waiting
> for as described here: [1] Jörn-Ingo is there an ETA?
>
> The other changes that are already done are:
> * strongswan 5.0.4 (security fix for EC cryptography with openssl)
> * openvpn: Disabling client connection working again
> * New status bar at the bottom of the web GUI
> * connection tracking list is sortable
> * Various hardware fixes: Intel MEI, PXE installation and USB keyboards
> * rrdtool: Fix monospace font
>
> New packages:
> * sysbench
> * VDR update coming
>
> The schedule (that is to be discussed):
> * Get the final fix for the update accelerator GUI done until this
> Friday (10th May 2013)
> * Upload the update to the testing tree on the weekend
> * Test during the week
> * If everything looks fine, we will release the following weekend
> * If not, fix, have another week for testing, then release
>
> If this is not working for anyone of you, please raise you hand.
> Otherwise, please help testing.
>
> -Michael
>
> [1] http://lists.ipfire.org/pipermail/development/2013-April/000363.html
>
> _______________________________________________
> Development mailing list
> Development(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/development
prev parent reply other threads:[~2013-05-11 9:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-08 13:19 Michael Tremer
2013-05-11 9:34 ` Michael Tremer [this message]
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=1368264896.1869.92.camel@rice-oxley.tremer.info \
--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