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: Planning Core Update 155
Date: Mon, 15 Mar 2021 13:48:08 +0000	[thread overview]
Message-ID: <FB4D2101-88C1-4BE7-B6E3-E71FEE46AB1A@ipfire.org> (raw)
In-Reply-To: <bea629b8-05d2-3849-c7a5-c5de87c5d904@ipfire.org>

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

Hello,

Okay, unless they are critical, I would propose to move them to the next update then.

I will close the update today then and upload it into testing and prepare a testing announcement as soon as possible.

Best,
-Michael

> On 14 Mar 2021, at 13:03, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
> 
> Hi All,
> 
> There are new versions of acl, attr and sudo available now.
> 
> I have checked them out and none of the changes require urgent implementation and so I will hold them until Core 155 has been released for testing.
> 
> The acl and attr changes have been worked on over the last 3 to 4 years.
> 
> Sudo has been worked on over the last three months. It covers minor bug fixes. I have checked through all changes and I did not find anything that would suggest urgent implementation is required.
> 
> 
> Regards,
> 
> Adolf.
> 
> On 12/03/2021 15:23, Adolf Belka wrote:
>> Hi all,
>> 
>> On 10/03/2021 14:38, Michael Tremer wrote:
>>> Hello everyone,
>>> 
>>> I wanted to open a quick thread to organise what is going into the next Core Update which I planned on closing soon so that people have more time to test the ALG changes that have been announced yesterday:
>>> 
>>> https://blog.ipfire.org/post/security-announcement-mitigating-nat-slipstreaming
>>> 
>>> It was being quiet and so I wanted to wait until armv5tel finally builds again and then branch the update. Now there is a massive wave of packages from Adolf which should probably be included in this release. Just to keep the backlog as small as possible.
>>> 
>>> Does anybody else have any pending changes that should go into c155?
>> I don't currently have any additional ones. I found most of the previous ones because they were updated in my Arch Linux systems so that flagged me to check them in IPFire.
>> 
>> If I find any new ones I will hold them till Core 155 has been issued for testing.
>> 
>> Regards,
>> 
>> Adolf.
>> 
>>> Best,
>>> -Michael
>> 
> -- 
> Sent from my laptop
> 


      reply	other threads:[~2021-03-15 13:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-10 13:38 Michael Tremer
2021-03-12 14:23 ` Adolf Belka
2021-03-14 13:03   ` Adolf Belka
2021-03-15 13:48     ` Michael Tremer [this message]

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=FB4D2101-88C1-4BE7-B6E3-E71FEE46AB1A@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