From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bernhard Bitsch To: development@lists.ipfire.org Subject: Aw: Re: IPFire 2.17 - Core Update 91 release schedule Date: Thu, 11 Jun 2015 15:55:56 +0200 Message-ID: In-Reply-To: <1434015960.25208.221.camel@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============8895369531319730060==" List-Id: --===============8895369531319730060== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi, a thread in the forum showed up a little issue in our tests. Some parts, don't know how many, just have a status of "untouched for a long = time". This is mainly true for Perl scripts in the WUI. I would be a big effort to check all this files. But some issues will come in sight, if at least during test period these file= s contain the lines use strict; use warnings; use CGI::Carp 'fatalsToBrowser'; Perl does tolerate so much dirty coding. In such cases it isn't sure whether = the intentions of the programmer meet the interpretation of the interpreter. These three lines force a check and log possible errors to the WUI. I fear, without these statements a couple of faulty test cases are reported a= s error-free. Bernhard > Gesendet: Donnerstag, 11. Juni 2015 um 11:46 Uhr > Von: "Michael Tremer" > An: "Jan Lentfer" > Cc: "development(a)lists.ipfire.org" > Betreff: Re: IPFire 2.17 - Core Update 91 release schedule > > Hello, >=20 > just follow this guide: >=20 > http://wiki.ipfire.org/en/configuration/ipfire/pakfire/testing >=20 > -Michael >=20 > On Thu, 2015-06-11 at 11:44 +0200, Jan Lentfer wrote: > > Hi, could you shortly describe (possibly once more) how can follow the te= sting branch instead of the stable branch? TIA Jan > >=20 > > Von meinem iPad gesendet > >=20 > > > Am 11.06.2015 um 10:51 schrieb Michael Tremer : > > >=20 > > > Hello, > > >=20 > > > I just wanted to update you quickly about the upcoming Core Update 91 > > > release plan. > > >=20 > > > 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. > > >=20 > > > 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. > > >=20 > > > 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. > > >=20 > > > We will push that build to the testing tree so that as many people can > > > help testing as possibly can. > > >=20 > > > If everything goes well we intend to release the final update 24 hours > > > after that - which will be Saturday some time after mid day. > > >=20 > > > Best, > > > -Michael > > >=20 > > > 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. >=20 --===============8895369531319730060==--