public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Core Update 157
Date: Tue, 18 May 2021 09:53:14 +0100	[thread overview]
Message-ID: <EA624EF9-1FC9-4642-8827-09FA26DFD0AE@ipfire.org> (raw)
In-Reply-To: <7a3cb033-f747-7bc0-1f09-6284906346fd@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 3002 bytes --]

Hello,

> On 17 May 2021, at 23:02, Peter Müller <peter.mueller(a)ipfire.org> wrote:
> 
> Hello Michael,
> 
> it just occurred to me that there are two patches fixing a nasty bug in fwhosts.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.

A timeout cannot be taken as an acknowledgement. Did you try getting in touch with Alex?

-Michael

> Shall we merge them anyway?
> 
> Thanks, and best regards,
> Peter Müller
> 
> 
>> Hello,
>> 
>>> On 17 May 2021, at 22:28, Peter Müller <peter.mueller(a)ipfire.org> wrote:
>>> 
>>> Hello Michael,
>>> 
>>> thanks for your message.
>>> 
>>> I am currently working on dropping all the packages and add-ons, as we discussed earlier
>>> this month. A patchset will be ready within the next few hours, ideally before midnight,
>>> Deo volente.
>> 
>> Cool. Thank you. This won’t make it into Core Update 157 because I want to allow some time for discussion.
>> 
>>> Aside from that, I do not have anything stable enough to make it into Core Update 158.
>> 
>> Thanks for letting me know :)
>> 
>> -Michael
>> 
>>> Thanks, and best regards,
>>> Peter Müller
>>> 
>>> 
>>>> 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 investigate 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 time 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 anything 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? Otherwise 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 hopefully 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.ipfire.org/devel/telco/2021-05-03)?
>>>> * VPNs for iOS (https://patchwork.ipfire.org/project/ipfire/list/?series=1323)?
>>>> 
>>>> What else are you guys working on that is ready for prime-time?
>>>> 
>>>> -Michael
>>>> 
>> 


  reply	other threads:[~2021-05-18  8:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-17 21:23 Michael Tremer
2021-05-17 21:28 ` Peter Müller
2021-05-17 21:29   ` Michael Tremer
2021-05-17 22:02     ` Peter Müller
2021-05-18  8:53       ` Michael Tremer [this message]
2021-05-17 21:52 ` Adolf Belka
2021-05-17 21:53   ` Michael Tremer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=EA624EF9-1FC9-4642-8827-09FA26DFD0AE@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox