From mboxrd@z Thu Jan  1 00:00:00 1970
From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: The Upcoming Core Update(s)
Date: Tue, 07 Nov 2023 22:10:57 +0100
Message-ID: <9ca9fc34-e5ce-49b4-9733-0a04394c1eee@ipfire.org>
In-Reply-To: <a0a23507-eddb-48f1-baba-ee5d926d0414@ipfire.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============7083755687764476608=="
List-Id: <development.lists.ipfire.org>

--===============7083755687764476608==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Hi Michael,

I am back from my holiday trip visiting my family and friends in the UK.

I will be working again on the OpenVPN package but that won't be ready for CU=
182.

I am currently working through about 20 package updates which should get subm=
itted over the next couple of days.

I have some minor bug fixes that may get submitted in time for CU182.

Overall, for CU182, there is nothing critical that I am working on beyond nor=
mal package updates, so you can decide form the patches I submit what to use =
and what to leave for a following CU.


Regards,

Adolf.


On 07/11/2023 19:22, Peter M=C3=BCller wrote:
> Hello Michael,
> hello *,
>
>> Hello everyone,
>>
>> Since this month=E2=80=99s video conference has been canceled, here is a c=
ouple of updates from my side:
>>
>> * Core Update 181 has been branched yesterday. I have this running in my o=
ffice for a little while and it seems to be a solid update. It also has a lot=
 of security fixes, so please give it a good test that we can hopefully relea=
se this in two weeks.
> indeed, Core Update 181 seems to work fine without any hiccups whatsoever. =
:-)
>
>> * For the following update(s): what do we have in the pipeline? Just to co=
ordinate that we don=E2=80=99t have too much in one update :)
> Unless we have more pressing things on our agenda, I remember Adolf saying
> that there are still a couple of packages, particularly libraries, which he
> did not had the resources to work through. At some point, it might be sensi=
ble
> to have something like a distributed mini-hackathon to ensure that everythi=
ng
> we include is at least roughly up to date, and if it's just by slicing the
> package list and distribute the shares. :-)
>
> At some point, I had the idea to keep an eye on various security advisories
> published by other distributions to identify non-prolific packages with
> important updates that might otherwise have flown under our radar, but this
> approach never worked well...
>
> Aside from updating, I recall Stefan working on porting firewall groups to
> ipset a while ago. Perhaps this is something we can then focus on to push
> out of the door next?
>
> Just my two cents. I currently do not have anything major on my docket list
> for IPFire 2.x. :-)
>
> All the best,
> Peter M=C3=BCller

--===============7083755687764476608==--