public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Rod Rodolico <rodo@dailydata.net>
To: development@lists.ipfire.org
Subject: Re: IPFire 2.17 - Core Update 91 release schedule
Date: Thu, 11 Jun 2015 10:55:53 -0500	[thread overview]
Message-ID: <5579AF89.9040208@dailydata.net> (raw)
In-Reply-To: <1434012671.25208.211.camel@ipfire.org>

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

Michael,

I for one appreciate this kind of message. It lets me plan my testing
and deployment planning.

Thank you,

Rod

On 06/11/2015 03:51 AM, Michael Tremer wrote:
> Hello,
> 
> I just wanted to update you quickly about the upcoming Core Update 91
> release plan.
> 
> There will be a new OpenSSL release at some time today (Thursday) which
> fixes several security vulnerabilities in this library. We do not know
> much about the severity of those vulnerabilities, yet, but we will
> release a new Core Update any ways.
> 
> The changes that have been pushed into the next branch will be released
> as well with an exception of Python. The Python package won't build on
> some systems and due to lack of time to debug this properly the Python
> update has been postponed.
> 
> As soon as the OpenSSL update is released we will start the build. We
> expect this to be late at night (as it has been in the past) and
> therefore the will be a build available Friday morning/noon European
> time. The ARM build will take much longer to complete though.
> 
> We will push that build to the testing tree so that as many people can
> help testing as possibly can.
> 
> If everything goes well we intend to release the final update 24 hours
> after that - which will be Saturday some time after mid day.
> 
> Best,
> -Michael
> 
> P.S. I was asked to send a short release plan for Core Updates on this
> list because it is not so easy to find out what the current status is
> sometimes. I would like your feedback about if this is a good idea and
> if this is helping. I am hoping that it is helping us to engage more
> testers into the testing procedure of new Core Updates and let you plan
> some time for doing that.
> 

-- 
Rod Rodolico
Daily Data, Inc.
POB 140465
Dallas TX 75214-0465
214.827.2170
http://www.dailydata.net

  reply	other threads:[~2015-06-11 15:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-11  8:51 Michael Tremer
2015-06-11 15:55 ` Rod Rodolico [this message]
2015-06-11 20:39   ` Michael Tremer
2015-06-12 15:15     ` Michael Tremer
2015-06-13 13:20       ` Arne Fitzenreiter
2015-06-12 20:42     ` Arne Fitzenreiter
2015-06-13  5:51       ` Stefan Schantl
     [not found] <6A691F9C-E1A7-480E-8D1E-12A37DD544C8@web.de>
2015-06-11  9:46 ` Michael Tremer
     [not found] <CAFHX57dDn27REQhoqBysqwZKCmTB72fxXKFtaFHPcqTW-wtqOg@mail.gmail.com>
2015-06-11 11:52 ` Michael Tremer
2015-06-12 16:10 Paul Simmons

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=5579AF89.9040208@dailydata.net \
    --to=rodo@dailydata.net \
    --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