Release goals for 22.XX

Hi, The OpenWrt 21.02 release is done and we should plan the next release. We already talked about this in the last meeting, see https://openwrt.org/meetings/20210920 To monitor the current state I created this wiki page based on the wiki page from the previous release: https://openwrt.org/d

Re: Release goals for 22.XX

Hi Hauke, Op woensdag 29 september 2021 om 22u28 schreef Hauke Mehrtens : Hi, The OpenWrt 21.02 release is done and we should plan the next release. We already talked about this in the last meeting, see https://openwrt.org/meetings/20210920 To monitor the current state I created this wiki p

Re: Release goals for 22.XX

On 9/29/21 10:43 PM, Stijn Segers wrote: Hi Hauke, Op woensdag 29 september 2021 om 22u28 schreef Hauke Mehrtens : Hi, The OpenWrt 21.02 release is done and we should plan the next release. We already talked about this in the last meeting, see https://openwrt.org/meetings/20210920 To monit

Re: Release goals for 22.XX

On 9/29/21 22:28, Hauke Mehrtens wrote: kernel 5.10: We should get all targets to kernel 5.10. All targets which are not on kernel 5.10 when we branch off should get removed. Kernel 5.15 could be also a LTS Kernel that should be released in the end of October? Why not aiming for it if we plan

Re: Release goals for 22.XX

Hauke: My thanks also for writing up those note. My desire would be to name our next release "22.03", with a target release date in March 2022. And we should name the following release "22.09" with a release date in September. And so on - every six months (or whatever interval we believe we

Re: Release goals for 22.XX

Rich Brown wrote: > - Having a firm feature freeze date decreases stress. If a particular > feature is done/substantially working, it goes in. If it's not quite > ready, it can skip this release, and get into the next release. (The > alternative is what I think happened with DSA.

Re: Release goals for 22.XX

On 30/09/2021 01:19, Nick wrote: > On 9/29/21 22:28, Hauke Mehrtens wrote: > >> kernel 5.10: >> We should get all targets to kernel 5.10. All targets which are not >> on kernel 5.10 when we branch off should get removed. > Kernel 5.15 could be also a LTS Kernel that should be released in the > end

Re: Release goals for 22.XX

On Thu, Sep 30, 2021 at 09:18:06PM +0300, Stijn Tintel wrote: > On 30/09/2021 01:19, Nick wrote: > > On 9/29/21 22:28, Hauke Mehrtens wrote: > > > >> kernel 5.10: > >> We should get all targets to kernel 5.10. All targets which are not > >> on kernel 5.10 when we branch off should get removed. > >

Re: Release goals for 22.XX

On 9/30/21 21:43, Daniel Golle wrote: On Thu, Sep 30, 2021 at 09:18:06PM +0300, Stijn Tintel wrote: On 30/09/2021 01:19, Nick wrote: On 9/29/21 22:28, Hauke Mehrtens wrote: kernel 5.10: We should get all targets to kernel 5.10. All targets which are not on kernel 5.10 when we branch off sho

Re: Release goals for 22.XX

On 9/30/21 10:01, Nick wrote: On 9/30/21 21:43, Daniel Golle wrote: On Thu, Sep 30, 2021 at 09:18:06PM +0300, Stijn Tintel wrote: On 30/09/2021 01:19, Nick wrote: On 9/29/21 22:28, Hauke Mehrtens wrote: kernel 5.10: We should get all targets to kernel 5.10. All targets which are not on ke

Re: Release goals for 22.XX

(I'm cc'ing both openwrt-devel and openwrt-adm since both will be involved in the decision) > On Sep 29, 2021, at 4:28 PM, Hauke Mehrtens wrote: > > The OpenWrt 21.02 release is done and we should plan the next release. > We already talked about this in the last meeting, see > https://openwrt.

Re: Release goals for 22.XX

On Thu, Sep 30, 2021 at 1:05 PM Nick wrote: > > > On 9/30/21 21:43, Daniel Golle wrote: > > On Thu, Sep 30, 2021 at 09:18:06PM +0300, Stijn Tintel wrote: > >> On 30/09/2021 01:19, Nick wrote: > >>> On 9/29/21 22:28, Hauke Mehrtens wrote: > >>> > kernel 5.10: > We should get all targets t

Re: Release goals for 22.XX

From: Rosen Penev To: Nick Cc: OpenWrt Development List Subject: Re: Release goals for 22.XX On Thu, Sep 30, 2021 at 1:05 PM Nick wrote: On 9/30/21 21:43, Daniel Golle wrote: On Thu, Sep 30, 2021 at 09:18:06PM +0300, Stijn Tintel wrote: On 30/09/2021 01:19, Nick wrote: On 9/29/21 22:28

Re: Release goals for 22.XX

On 9/30/21 10:40 PM, Paul Spooren wrote: On 9/30/21 10:01, Nick wrote: On 9/30/21 21:43, Daniel Golle wrote: On Thu, Sep 30, 2021 at 09:18:06PM +0300, Stijn Tintel wrote: On 30/09/2021 01:19, Nick wrote: On 9/29/21 22:28, Hauke Mehrtens wrote: kernel 5.10: We should get all targets to ker

Re: Release goals for 22.XX

On 9/30/21 3:34 AM, Rich Brown wrote: Hauke: My thanks also for writing up those note. My desire would be to name our next release "22.03", with a target release date in March 2022. And we should name the following release "22.09" with a release date in September. And so on - every six mon

Re: Release goals for 22.XX

On Fri, Oct 1, 2021 at 3:05 PM Hauke Mehrtens wrote: > > On 9/30/21 10:40 PM, Paul Spooren wrote: > > > > On 9/30/21 10:01, Nick wrote: > >> > >> On 9/30/21 21:43, Daniel Golle wrote: > >>> On Thu, Sep 30, 2021 at 09:18:06PM +0300, Stijn Tintel wrote: > On 30/09/2021 01:19, Nick wrote: >

Re: Release goals for 22.XX

Il giorno sab 2 ott 2021 alle ore 01:35 Rosen Penev ha scritto: > > On Fri, Oct 1, 2021 at 3:05 PM Hauke Mehrtens wrote: > > > > On 9/30/21 10:40 PM, Paul Spooren wrote: > > > > > > On 9/30/21 10:01, Nick wrote: > > >> > > >> On 9/30/21 21:43, Daniel Golle wrote: > > >>> On Thu, Sep 30, 2021 at 0

Re: Release goals for 22.XX

Hi all, based on my overview[1] things are moving forward and being tested, great! What about the targets that did not see any 5.10 ambitions yet? Specifically: - arc770 - archs38 - ath25 - bcm47xx - bcm4908 - ipq807x - layerscape - pistachio - uml Is anyone aware of people working on those

Re: Release goals for 22.XX

On Wed, 6 Oct 2021 at 00:08, Paul Spooren wrote: > > Hi all, > > based on my overview[1] things are moving forward and being tested, > great! What about the targets that did not see any 5.10 ambitions yet? > Specifically: > > - arc770 > - archs38 > - ath25 > - bcm47xx > - bcm4908 > - ipq807x I ca

Re: Release goals for 22.XX

> On 5. Oct 2021, at 12:33, Robert Marko wrote: > > On Wed, 6 Oct 2021 at 00:08, Paul Spooren wrote: >> >> Hi all, >> >> based on my overview[1] things are moving forward and being tested, >> great! What about the targets that did not see any 5.10 ambitions yet? >> Specifically: >> >> - ar

Re: Release goals for 22.XX

On 30.09.2021 03:34, Rich Brown wrote: My desire would be to name our next release "22.03", with a target release date in March 2022. And we should name the following release "22.09" with a release date in September. And so on - every six months (or whatever interval we believe we can susta

Re: Release goals for 22.XX

> On Oct 6, 2021, at 1:58 AM, Rafał Miłecki wrote: > > On 30.09.2021 03:34, Rich Brown wrote: >> My desire would be to name our next release "22.03", with a target release >> date in March 2022. And we should name the following release "22.09" with a >> release date in September. And so on

Re: Release goals for 22.XX

Wise words from the experienced! If making a yearly release is unattainable, isn't making point releases more achievable? Even if it's adding a single commit, point releases send a signal to the outside world that the project is still active, and e.g. that security is in focus. Any point rele

Re: Release goals for 22.XX

Paul, Rafał, I think our emails passed in the ether... (http://lists.openwrt.org/pipermail/openwrt-devel/2021-October/036637.html) As I said in that message, I am very aware of the time constraints of the volunteers for OpenWrt. And I don't mean to suck the conversation into "grand strategies

Re: Release goals for 22.XX

Hi, Rich, On Wed, 6 Oct 2021 at 17:54, Rich Brown wrote: > > Paul, Rafał, > > I think our emails passed in the ether... > (http://lists.openwrt.org/pipermail/openwrt-devel/2021-October/036637.html) > > As I said in that message, I am very aware of the time constraints of the > volunteers for Op

Re: Release goals for 22.XX

On Wed, Oct 6, 2021 at 10:46 AM Rui Salvaterra wrote: > > Hi, Rich, > > On Wed, 6 Oct 2021 at 17:54, Rich Brown wrote: > > > > Paul, Rafał, > > > > I think our emails passed in the ether... > > (http://lists.openwrt.org/pipermail/openwrt-devel/2021-October/036637.html) > > > > As I said in that

Re: Release goals for 22.XX

The below is a fairly prescient analysis of the situation, and a good approach, Rui. I think openwrt will be fine staying put on iptables, until bpfilter matures. I think I have about 20 individual rules on my FW. Having the capability is nice, but most home users probably don't have or need 10

Re: Release goals for 22.XX

On 10/6/21 12:33 AM, Robert Marko wrote: On Wed, 6 Oct 2021 at 00:08, Paul Spooren wrote: Hi all, based on my overview[1] things are moving forward and being tested, great! What about the targets that did not see any 5.10 ambitions yet? Specifically: - arc770 - archs38 - ath25 - bcm47xx - bc

Re: Release goals for 22.XX

On Thu, 7 Oct 2021 at 00:33, Hauke Mehrtens wrote: > > On 10/6/21 12:33 AM, Robert Marko wrote: > > On Wed, 6 Oct 2021 at 00:08, Paul Spooren wrote: > >> > >> Hi all, > >> > >> based on my overview[1] things are moving forward and being tested, > >> great! What about the targets that did not see

Re: Release goals for 22.XX

Hi, --- %< --- based on my overview[1] things are moving forward and being tested, great! What about the targets that did not see any 5.10 ambitions yet? Specifically: - arc770 - archs38 I just got an email from synopsys and they'll contribute Kernel 5.10 patches for

Re: Release goals for 22.XX

Hi, Paul, On Fri, 8 Oct 2021 at 10:14, Paul Spooren wrote: > > > > - ath25 > > > Could this be dropped? Nothing in this target has more than 32 MiB of RAM (most devices have 16 MiB) [1]. Just put it out of its misery. :) [1] https://openwrt.org/?do=showtag&tag=ath25 Cheers, Rui __

Re: Release goals for 22.XX

pt., 8 paź 2021 o 11:16 Paul Spooren napisał(a): > > Hi, > Hi Paul > --- %< --- > > > > based on my overview[1] things are moving forward and being tested, > > great! What about the targets that did not see any 5.10 ambitions > > yet? > > Specifically: > > > > - arc770 > >

Re: Release goals for 22.XX

Hi, Paul, On Fri, 8 Oct 2021 at 11:09, Rui Salvaterra wrote: > > Nothing in this target has more than 32 MiB of RAM (most devices have > 16 MiB) [1]. Just put it out of its misery. :) Scratch that. After chatting with dangole, there may be some life in it, after all. I have an ath25 device (FON2

Re: Release goals for 22.XX

Hi Paul, On 10/8/21 11:13 AM, Paul Spooren wrote: Hi,     - bcm47xx     - bcm4908 Will these two targets be replaced by bmips? bmips is for big endian BCM33xx, BCM63xx and BCM7xxx MIPS chips. bcm47xx is little endian MIPS form a different product line. bcm4908 is ARM based. When I find s

Re: Release goals for 22.XX

On 2021-10-08 11:13, Paul Spooren wrote: Hi, --- %< --- based on my overview[1] things are moving forward and being tested, great! What about the targets that did not see any 5.10 ambitions yet? Specifically: - arc770 - archs38 I just got an email from synopsys and

Re: Release goals for 22.XX

Hello Rui, On Fri, Oct 8, 2021 at 4:40 PM Rui Salvaterra wrote: > On Fri, 8 Oct 2021 at 11:09, Rui Salvaterra wrote: >> Nothing in this target has more than 32 MiB of RAM (most devices have >> 16 MiB) [1]. Just put it out of its misery. :) > > Scratch that. After chatting with dangole, there may

Re: Release goals for 22.XX

> "Sergey" == Sergey Ryazanov writes: Sergey> I am in the process of migrating ath25 to the 5.10 Sergey> kernel. Initial build was trivial. But I need to restore the Sergey> Marvel swconfig driver that was lost during the initial 5.10 Sergey> kernel introduction, and carefully run-time test i

Re: Release goals for 22.XX

On 10/9/21 9:57 PM, Russell Senior wrote: "Sergey" == Sergey Ryazanov writes: Sergey> I am in the process of migrating ath25 to the 5.10 Sergey> kernel. Initial build was trivial. But I need to restore the Sergey> Marvel swconfig driver that was lost during the initial 5.10 Sergey> kernel int

Re: Release goals for 22.XX

Hi, Sergey, On Sun, 10 Oct 2021 at 01:43, Sergey Ryazanov wrote: > > I am in the process of migrating ath25 to the 5.10 kernel. Initial > build was trivial. But I need to restore the Marvel swconfig driver > that was lost during the initial 5.10 kernel introduction, and > carefully run-time test

Re: Release goals for 22.XX

On 10/10/21 2:44 AM, Sergey Ryazanov wrote: Hello Rui, On Fri, Oct 8, 2021 at 4:40 PM Rui Salvaterra wrote: On Fri, 8 Oct 2021 at 11:09, Rui Salvaterra wrote: Nothing in this target has more than 32 MiB of RAM (most devices have 16 MiB) [1]. Just put it out of its misery. :) Scratch that.

Re: Release goals for 22.XX

Hi On 2021-10-10, Hauke Mehrtens wrote: > On 10/10/21 2:44 AM, Sergey Ryazanov wrote: > > On Fri, Oct 8, 2021 at 4:40 PM Rui Salvaterra wrote: > >> On Fri, 8 Oct 2021 at 11:09, Rui Salvaterra wrote: [...] > > I am in the process of migrating ath25 to the 5.10 kernel. Initial > > build was trivia

Re: Release goals for 22.XX

On Mon, Oct 11, 2021 at 12:12 AM Hauke Mehrtens wrote: > On 10/10/21 2:44 AM, Sergey Ryazanov wrote: >> On Fri, Oct 8, 2021 at 4:40 PM Rui Salvaterra wrote: >>> On Fri, 8 Oct 2021 at 11:09, Rui Salvaterra wrote: Nothing in this target has more than 32 MiB of RAM (most devices have 16 M

Re: Release goals for 22.XX

On 10/14/21 12:03 AM, Sergey Ryazanov wrote: On Mon, Oct 11, 2021 at 12:12 AM Hauke Mehrtens wrote: On 10/10/21 2:44 AM, Sergey Ryazanov wrote: On Fri, Oct 8, 2021 at 4:40 PM Rui Salvaterra wrote: On Fri, 8 Oct 2021 at 11:09, Rui Salvaterra wrote: Nothing in this target has more than 32 Mi

Re: Release goals for 22.XX

Hi On 2021-10-14, Sergey Ryazanov wrote: > On Mon, Oct 11, 2021 at 12:12 AM Hauke Mehrtens wrote: > > On 10/10/21 2:44 AM, Sergey Ryazanov wrote: > >> On Fri, Oct 8, 2021 at 4:40 PM Rui Salvaterra > >> wrote: > >>> On Fri, 8 Oct 2021 at 11:09, Rui Salvaterra wrote: [...] > > Does it make sense

Re: Release goals for 22.XX

On 10/5/21 12:32 PM, camden lindsay wrote: Is - ipq807x  a typo? i don't see this target in the snapshots... is it really ipq806x? many thanks On Tue, Oct 5, 2021 at 3:14 PM Paul Spooren > wrote: Hi all, based on my overview[1] things are moving forward an

Re: Release goals for 22.XX

On 2021-10-20 04:47, Paul Spooren wrote: For now layerscape is still on 5.4 without Kernel 5.10 support. Is anyone planing to add support? Please reach out. As I had already written on 08 October, I am already working on it. Thereby I try to bring all relevant components to the state of LSDK-21

Re: Release goals for 22.XX

Hi Martin, On 10/19/21 7:26 PM, Martin Schiller wrote: On 2021-10-20 04:47, Paul Spooren wrote: For now layerscape is still on 5.4 without Kernel 5.10 support. Is anyone planing to add support? Please reach out. As I had already written on 08 October, I am already working on it. Thereby I try

Re: Release goals for 22.XX - procd-seccomp and procd-ujail

On 9/29/21 10:28, Hauke Mehrtens wrote: Hi, The OpenWrt 21.02 release is done and we should plan the next release. We already talked about this in the last meeting, see https://openwrt.org/meetings/20210920 To monitor the current state I created this wiki page based on the wiki page from t

Re: Release goals for 22.XX - procd-seccomp and procd-ujail

On 07/10/21 08:51, Paul Spooren wrote: On 9/29/21 10:28, Hauke Mehrtens wrote: Hi, The OpenWrt 21.02 release is done and we should plan the next release. We already talked about this in the last meeting, see https://openwrt.org/meetings/20210920 To monitor the current state I created thi

Re: Release goals for 22.XX - procd-seccomp and procd-ujail

On 10/7/21 8:51 AM, Paul Spooren wrote: On 9/29/21 10:28, Hauke Mehrtens wrote: Hi, The OpenWrt 21.02 release is done and we should plan the next release. We already talked about this in the last meeting, see https://openwrt.org/meetings/20210920 To monitor the current state I created this

Re: Release goals for 22.XX - procd-seccomp and procd-ujail

On 10/7/21 8:31 AM, Hauke Mehrtens wrote: On 10/7/21 8:51 AM, Paul Spooren wrote: On 9/29/21 10:28, Hauke Mehrtens wrote: Hi, The OpenWrt 21.02 release is done and we should plan the next release. We already talked about this in the last meeting, see https://openwrt.org/meetings/20210920