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-testing Best, -Michael On Thu, 2015-06-11 at 10:55 -0500, Rod Rodolico wrote: > 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. > > >