Re: IPFire 2.17 - Core Update 91 release schedule

[Michael Tremer <michael.tremer@ipfire.org>]

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

Hello,

just follow this guide:

http://wiki.ipfire.org/en/configuration/ipfire/pakfire/testing

-Michael

On Thu, 2015-06-11 at 11:44 +0200, Jan Lentfer wrote:
> Hi, could you shortly describe (possibly once more) how can follow the testing branch instead of the stable branch? TIA Jan
> 
> Von meinem iPad gesendet
> 
> > Am 11.06.2015 um 10:51 schrieb Michael Tremer <michael.tremer(a)ipfire.org>:
> > 
> > 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.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]