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: Release schedule for Core Update 165 and 166 Date: Wed, 23 Feb 2022 17:07:26 +0000 Message-ID: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2095612829186430878==" List-Id: --===============2095612829186430878== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello *, for everyone's information: A few days after scheduled, the merge window for Core Update 165 is now close= d. As mentioned earlier, it will now be in the bugfixing phase until March 12th = or so. For Core Update 166, I just created a temporary personal branch: https://git.ipfire.org/?p=3Dpeople/pmueller/ipfire-2.x.git;a=3Dshortlog;h=3Dr= efs/heads/temp-c166-development The vast majority of patches currently being tracked at https://patchwork.ipf= ire.org/project/ipfire/list/ is staged, which means they will go into Core Update 165. A handful of patches remained, either because they were not reviewed by anybody, do not apply anym= ore, or appear to be superseded/orphaned. I will go through these and write a dedicated mail about what to do with them from my point of view. Thanks, and best regards, Peter M=C3=BCller --===============2095612829186430878==--