From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adolf Belka To: development@lists.ipfire.org Subject: Re: Release schedule for Core Update 165 and 166 Date: Mon, 14 Feb 2022 22:43:44 +0100 Message-ID: <9e2827ac-3788-721f-cf1f-2f53fcb85bd9@ipfire.org> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============8888684371182492418==" List-Id: --===============8888684371182492418== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi Peter, On 14/02/2022 20:27, Peter M=C3=BCller wrote: > Hello development folks, > > to make it more clear which patch goes into which release, at which point i= n time > a Core Update will be closed, and to ideally release stuff ready to go fast= er, 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 tha= t 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" sh= ortly, > closing the "merge window" (in which I pick up patches from https://patc= hwork.ipfire.org/) > by the end of this week. > > - Afterwards, Core Update 165 will go into the bugfixing phase for 20 days,= until > March 12nd. > > - It will then be released for the public testing phase for 10 days, being = released > as stable at approximately March 22nd. At the same time, I will start wo= rking on > Core Update 166. > > For personal reasons, I currently lack oversight over my available for t= he project > in March, and will assign Core Update 166 to somebody else if I cannot t= ake properly > care of it. > > While this sounds a bit rush and complex (to myself as well), I think it is= worth > a try. After all, I consider these dates being rough deadlines, and anythin= g major > will (have to) be an exception to this schedule. Just let's see how it work= s 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 rev= iewing patches; > some of the 203 patches currently tracked in https://patchwork.ipfire.org/p= roject/ipfire/list/ > have not been reviewed yet. I have had a scan through and reviewed the ones that I feel comfortable that = I understand and that my review makes sense. I also think that I shouldn't/ca= n't review my own patches so someone else will have to have a look at those. > Thanks, and best regards, > Peter M=C3=BCller --===============8888684371182492418==--