From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter =?utf-8?q?M=C3=BCller?= To: development@lists.ipfire.org Subject: Re: Core Update 157 Date: Tue, 18 May 2021 00:02:58 +0200 Message-ID: <7a3cb033-f747-7bc0-1f09-6284906346fd@ipfire.org> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============5059055281050822470==" List-Id: --===============5059055281050822470== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello Michael, it just occurred to me that there are two patches fixing a nasty bug in fwhos= ts.cgi still left in the queue: - https://patchwork.ipfire.org/patch/4199/ - https://patchwork.ipfire.org/patch/4206/ Since fwhosts.cgi was primarily written by Alex, I asked him to review these,= but have not heard anything back. Shall we merge them anyway? Thanks, and best regards, Peter M=C3=BCller > Hello, >=20 >> On 17 May 2021, at 22:28, Peter M=C3=BCller w= rote: >> >> Hello Michael, >> >> thanks for your message. >> >> I am currently working on dropping all the packages and add-ons, as we dis= cussed earlier >> this month. A patchset will be ready within the next few hours, ideally be= fore midnight, >> Deo volente. >=20 > Cool. Thank you. This won=E2=80=99t make it into Core Update 157 because I = want to allow some time for discussion. >=20 >> Aside from that, I do not have anything stable enough to make it into Core= Update 158. >=20 > Thanks for letting me know :) >=20 > -Michael >=20 >> Thanks, and best regards, >> Peter M=C3=BCller >> >> >>> Hello, >>> >>> Because there are so many things going on at the same time, I would like = to start a brief main thread about the upcoming Core Update(s). >>> >>> The original plan was to have this closed a while ago because Core Update= 156 has already gone out. But then I decided to wait for a couple of smaller= things until we had a security vulnerability reported which I wanted to inve= stigate more (#12616 and #12619). It is not too bad, but I would like to ship= at least a fix that is good enough to mitigate it. We might need some more t= ime to figure out the details around the other half of the solution for this = problem. >>> >>> Now this update has become *very* large. It is the largest update we have= ever had and that might break things. Therefore I do not want to merge anyth= ing more that has to go into the core system, but add-on packages are fine. >>> >>> In fact, the build that I just pushed should be the final one, unless we = find any other problems. Does anyone have anything urgent and small left? Oth= erwise Core Update 158 will be open as soon as 157 has hit the master branch. >>> >>> In order to coordinate that a little bit more and have a good and hopeful= ly brief merge window, what should be in it? >>> >>> * Fixes for #12616 >>> * Can we finish the migration away from Python 2? >>> * Drop the packages discussed at the last conference call (https://wiki.i= pfire.org/devel/telco/2021-05-03)? >>> * VPNs for iOS (https://patchwork.ipfire.org/project/ipfire/list/?series= =3D1323)? >>> >>> What else are you guys working on that is ready for prime-time? >>> >>> -Michael >>> >=20 --===============5059055281050822470==--