From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tremer To: development@lists.ipfire.org Subject: Re: IPFire 2.17 - Core Update 91 release schedule Date: Thu, 11 Jun 2015 22:39:56 +0200 Message-ID: <1434055196.25208.238.camel@ipfire.org> In-Reply-To: <5579AF89.9040208@dailydata.net> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6563331467739445088==" List-Id: --===============6563331467739445088== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello, the x86 build is done and uploaded. You can start testing now. Please report any issues if you find any. The change log is over here: http://planet.ipfire.org/post/ipfire-2-17-core-update-91-is-available-for-t= esting Best, -Michael On Thu, 2015-06-11 at 10:55 -0500, Rod Rodolico wrote: > Michael, >=20 > I for one appreciate this kind of message. It lets me plan my testing > and deployment planning. >=20 > Thank you, >=20 > Rod >=20 > On 06/11/2015 03:51 AM, Michael Tremer wrote: > > 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 >=20 --===============6563331467739445088== Content-Type: application/pgp-signature Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="signature.asc" MIME-Version: 1.0 LS0tLS1CRUdJTiBQR1AgU0lHTkFUVVJFLS0tLS0KVmVyc2lvbjogR251UEcgdjIKCmlRSWNCQUFC Q2dBR0JRSlZlZklnQUFvSkVJQjU4UDl2a0FrSFZKc1AvaTI3cjh2VmJvOVlWK1RGTjBxOWljUzUK dVVVcnlzMXhSQUgrUThBNHFpbmRUSDFjczZ4Mi9RNnZSQ05mUkZrcTNrd2dQUXdIeW5yVWcydnNI SElQdDZ4bApsS0g5dE9yNEpjTkRVdUdLOHRON3Z3eEIzWFlMR0Y3M2FTa0pjQW9KZ1pTZHFWVFU3 VndoNEs1SFd4K3Y3d0pNCjNXT0djSTU2L3BZb1hxVUxQdVcwbHFsYmllTTR4QTZJR0tRZWs5WEQr TkNzS25Dblc5N2FGUG5LOEpyaWFyYTIKSTEzZ08wLzhDeHpuQmRKVmRMZ2hYOVE3ajgwQnhCaDNT Vkd3Z0ZtNTRTSWFjY2liQXkyRzVNTzFBTUxMYXhkRApzUm1ET1V0UkliT0VXNFlMTjFUd0x2S0hE SnlaRmRZUmRKYXZWZXZLblBlNllmSks2bDUzem5qU0F2dGM2dVo3CmVpaGZBU1BGWHN3SFdydUwz amFsNFdCT0ZiK3NtSWpkNjlkSW9Way9FdjVMNlh0RWI4S0dlSGM4TkpFTDNGL1AKS1plQ1FwQm9V TGFYYThsT3M5Y1djNERIWEtlMHZCMlR0MFVvQTYxSFVBYWdRNUtaVlk0dFhWVVgwVDhpbWZDTQpR VTJSd3NVeEVTQUpGc1N4UEdwV3NreU1NMG1zVy9KRUd0S1hxOHhuN3FtaklVKzlaRHFBWld0QjBC RXVqMEJRClB1RHg0dlBDMGlXb1hDV2xtdDAvS2Uxb1Z0T0loVm1vWWNxWnl0WTVNWVo5RUNGOVRh cEx2YURDVTdPVWpyYWcKNWF4WjBCMllETlB3Y24rUWxOQnFSajljT2hwYTRLT3VHUit5ZFNRZDd1 ajV6TE8zVzMzVzRXd0tYbitKejJWMgpQeGxZQm1JeXcranJPOXR6WWgvdQo9Z2ZIeAotLS0tLUVO RCBQR1AgU0lHTkFUVVJFLS0tLS0K --===============6563331467739445088==--