From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter =?utf-8?q?M=C3=BCller?= To: development@lists.ipfire.org Subject: Release schedule for Core Update 165 and 166 Date: Mon, 14 Feb 2022 19:27:01 +0000 Message-ID: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1637368186190429064==" List-Id: --===============1637368186190429064== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello development folks, to make it more clear which patch goes into which release, at which point in = time a Core Update will be closed, and to ideally release stuff ready to go faster= , Michael and myself just had a phone call over the IPFire 2.x release schedule (see: https://wiki.ipfire.org/devel/release-schedule), and we decided to give that = another try. Having extended the "merge window" phase to 14 days, this means: - I will push my personal testing branch for Core Update 165 into "next" shor= tly, closing the "merge window" (in which I pick up patches from https://patchwo= rk.ipfire.org/) by the end of this week. - Afterwards, Core Update 165 will go into the bugfixing phase for 20 days, u= ntil March 12nd. - It will then be released for the public testing phase for 10 days, being re= leased as stable at approximately March 22nd. At the same time, I will start worki= ng on Core Update 166. For personal reasons, I currently lack oversight over my available for the = project in March, and will assign Core Update 166 to somebody else if I cannot take= properly care of it. While this sounds a bit rush and complex (to myself as well), I think it is w= orth a try. After all, I consider these dates being rough deadlines, and anything = major will (have to) be an exception to this schedule. Just let's see how it works = this time... :-) As always, feel free to drop me a line in case of any questions/trouble/etc. Also, it would be great if there could be some more people on this list revie= wing patches; some of the 203 patches currently tracked in https://patchwork.ipfire.org/pro= ject/ipfire/list/ have not been reviewed yet. Thanks, and best regards, Peter M=C3=BCller --===============1637368186190429064==--