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: Core Update 158 and beyond
Date: Tue, 22 Jun 2021 13:17:00 +0100	[thread overview]
Message-ID: <4EE7CE34-859D-4AA2-9CCD-26283357D7DB@ipfire.org> (raw)

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

Hello everyone,

Yesterday, I merged the upcoming Core Update into master so that we can finalise it for its release.

There are loads of changes in it that may require a little bit of extra testing. Especially the large amount of changes to the CGI files requires some extra love, so I hope that everyone of you can find a couple of minutes and click as many buttons as possible and see whether things are working fine. If not, please report here.

I will work on a change log as soon as possible and publish it on the blog as usual.

The next update will be put together by Arne who is now fully in charge of the next branch. It will come with the new kernel and to not make communication too difficult, he will just take charge and put the whole thing together.

We probably won’t have too much space because the kernel is going to be quite large. However, there will be a new toolchain and loads of other things coming with it, so if you have any patches towards that, please coordinate on the list and submit.

Of course I would like to know what everyone has in the pipeline so that we can schedule it accordingly.

Best,
-Michael

             reply	other threads:[~2021-06-22 12:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-22 12:17 Michael Tremer [this message]
     [not found] <28E9F021-D5D0-4F1E-BC69-53F8043E4E24@ipfire.org>
2021-06-26 12:26 ` Adolf Belka
2021-06-26 12:27   ` Michael Tremer
2021-06-28 11:18     ` Adolf Belka

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=4EE7CE34-859D-4AA2-9CCD-26283357D7DB@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