13:02:06 #startmeeting 13:02:06 Meeting started Sat Jan 29 13:02:06 2022 UTC. The chair is IgorPec. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:02:06 Useful Commands: #action #agreed #help #info #idea #link #topic. 13:02:30 #topic Welcome and check attendance 13:03:11 checked 13:03:28 Say hi, state which board / family you represent or/which task/role youre taking on. 13:03:41 Also if any new ppl are here, maybe add then you're new. 13:04:37 <-- infrastructure/evangelism/lifecoach 13:04:48 JetHome boards (JetHub D1/H1/etc) + some amlogic magic. 13:05:00 <-- mvebu and release planner 13:05:11 <-- somewhat-all meson64 and ODROID N2 / HC4 for these meeting purposes. I'm new to meetings. 13:05:38 rock3a and getting into automation engineer role 13:06:08 <-- no specific boards, feeling the gab, infrastructure 13:07:00 i'm new to meetings too) 13:07:07 hello! 13:07:44 Hi. Semi-AFK due to family duties. doing forum/discord/irc moderation 13:07:45 ok for the new ppl. we basically go over the board and feature status, check which big things will be in release and choose targets for next release cycle. 13:09:03 Ok biggest step I think was supported/WIP/CSC changes. I think that is done? 13:09:26 not completly, i would say its still wip 13:09:57 I saw support status between website and git is now synced? 13:10:18 relations between download - build framework and new maintainers needs to be synched and doublechedk and update when changes are needed 13:10:50 in the mean time some new folks showed up, so we are behind i would say 13:11:23 ok but download pages already show wips and generally much better. and there's new images since jan too. could you clarify? 13:11:48 #action WIP Changes - new maintainers needs to be synched and doublechedk and update when changes are needed; reconcile recent new maintainers 13:11:54 yes, i would open a task on "systematical check on statuses" 13:12:39 Also we need to add maintainer name to board config. This is something maintainers should IMHO PR by themselves for their board. 13:13:01 i have open a new repo https://github.com/armbian/internal 13:13:02 <08Tonymac32> Agreed 13:13:17 Also good @ igor. 13:13:18 yeah we've been a little soft on that, def should have that sorted before release 13:13:31 which is closed, to keep some internal stuff and that would be best to be there ( to get rid of googledocs) 13:13:57 Then we should make a post in announcements, and call out maintainers to add themselves via PR. 13:14:00 #action assure maintainer is in board config prior to release. Prefered that new maintainers perform this task themselves via PR 13:14:01 so this is just some base - each new maintaner should be listed there, 13:14:29 * rpardini plug: armbian-next would massively facilitate this 13:14:32 I would like to have them list themselves. To test commitment. (as lanefu #actioned). 13:15:25 also one meeting on the topic of board rules should be conducted. I am not sure they are clear to everyone 13:15:48 also perhaps some ideas for improvements can arrise 13:16:23 #action coordinate maintainer meeting to discuss mainatinership and process. mandatory for new maintaienrs 13:17:25 Any other overall project things to discuss? 13:17:34 o/ 13:17:39 hi trash 13:17:42 IgorPec will the board maintainers have access to the internal repository? 13:17:50 adeepv: yes 13:17:58 * TRS-80 was trying to raise his hand :) 13:18:07 TRS-80 go 13:18:47 its an older model, but it checks out. 13:19:18 I see a lot of applicants for e.g., Board Maintainer on the forums, should I approve them? Is there some process? Secret vote, discussion I am not aware of? 13:19:23 :D 13:19:36 i am slowly talking with them 13:19:52 i can forward you which are yet to be contacted 13:20:30 all that are not approved yet - go 13:20:32 Yes, I did not know if it was just a case of you being busy or what. I can make an effort to idle in IRC more, esp. in -onboarding channel if that helps. 13:20:35 We dont need a maintainer vote. If they can fulfill the requirements (board avail, etc). Then they can maintain. If they horribly break something we can still kick them 13:20:53 That's sort of what I was thinking, we could use the help. 13:20:58 Just wanted to check. 13:21:05 yes. its just some general welcoming and helping them around 13:21:13 That I can do. :) 13:21:17 yes. don't need to vote.... the guidance is losing maintainership role if they donpt participate 13:21:46 Yeah I figured, just wanted to make sure as I've been away a while. Did not know if there was policy. 13:21:53 cool 13:22:04 I'll get on it next login. 13:22:13 13:22:22 Ok checking Jira we look pretty good on overall release readiness https://armbian.atlassian.net/projects/AR/versions/10009/tab/release-report-all-issues 13:22:52 I guess AR1068 is done? https://armbian.atlassian.net/browse/AR-1068 13:22:53 4AR-1068 6[Task] "Add gnome-system-monitor to Focal and Jammy" reported by 3Igor Pecovnik at 2022-01-25. Status: To Do 13:23:04 yes, can move it to done 13:23:27 there are few bugs that need attention 13:23:54 Those seem family/board related though. No overall bugs? 13:24:26 overall - facebook login on forum is not working. if that counts 13:24:31 i think i forget to add it 13:24:34 f*ck fb 13:24:37 :) 13:24:50 I share your esteemed viewpoint. :) 13:25:19 I'd then go to topic per family and have maintainers speak up. 13:25:22 #topic Allwinner 13:25:56 a20 sata is broken 13:26:11 AR191? 13:26:13 yes 13:26:39 and AR-1075 13:26:39 4AR-1075 6[Bug] "Allwinner video driver bug" reported by 3Igor Pecovnik at 2022-01-29. Status: To Do 13:26:57 I don't have Allwinner HW. Who's maintaining them? 13:27:12 good question. not sure who to pin this 13:27:12 the maintainer hopefully 13:27:23 bananapipro igor xD 13:27:25 its for all boards 13:27:55 julia was debugging this recently, but she didn't get any further 13:28:14 whoever is the most active allwinner SME should own it then 13:28:18 Julia is new? 13:28:24 yes 13:28:37 juri_ 13:28:54 @juri_ any updates on that? 13:29:19 and the other bug is https://github.com/armbian/build/pull/3240 13:29:49 we have a solution but its a dirty hack 13:30:32 then there is AR-246 which needs to be verified, i suspect its no more 13:30:33 4AR-246 6[Bug] "SPI overlay seems to be broken" reported by 3Igor Pecovnik at 2020-05-16. Status: To Do 13:30:37 if we have a solution... just make a tech debt jira story for future release to un-dirty it 13:30:45 as a contigency 13:31:28 if we will wait long enough, solution will emerge upstream. this is how i understand that problem 13:31:50 this is all known for allwinner 13:31:56 except general 13:32:03 bumping u-boot and kernel 13:32:08 AR-1074 13:32:09 4AR-1074 6[Story] "Switch all CURRENT to 5.15.y and EDGE to 5.16.y" reported by 3Igor Pecovnik at 2022-01-29. Status: To Do 13:32:14 Yeah lets to that later. 13:32:21 #topic Amlogic 13:32:43 i think we need update kernels 13:32:53 to 5.15 - stable, 5.16 - edge 13:33:02 i'll only add AR-1071 13:33:03 4AR-1071 6[Bug] "Odroid N2 upgrade path is partially broken" reported by 3Igor Pecovnik at 2022-01-29. Status: To Do 13:33:42 <05fourheads> Are we keeping 5.4 kernels? 13:34:09 Can we please move general kernel discussion after the board/family topics. 13:34:19 ok so I've a long story, bear with me? 13:34:27 Is it on Amlogic? 13:34:28 fourheads: for amlogic or in general? 13:34:31 yes 13:34:33 In 26/September/2021, PR #3154 was merged into master. That stabilizes meson64-current 5.10.y quite a bit and somewhat makes ODROID usable. It also clears a lot of flak other meson64's were getting due to HK's patches. Also #3155 bumped meson64 to u-boot 2021.07 to match. (I guess there were JIRA about those, but can't find them. Sorry) 13:34:34 shoot 13:34:35 * TRS-80 sips his coffee 13:34:37 <05fourheads> In general 13:34:48 rpardini beer? yes) 13:35:09 We didn't have any release since then, I think, and until last week we had images from August/2021 on official download pages. There's now new images since last week, but I dunno which branch they were built from. 13:35:17 fourheads: in general we will discuss after hw specific 13:35:23 Unfortunately, in that move, edge kernel (5.15.y?) was left behind, full of weird patches and very unstable atleast for ODROIDs, and very possibly also for the other meson64s due to those infamous reboot hacks and other shit from HK; the comments in those PRs show the principle behind the clean up, but gotta find time and cycle my N2+ out of prod again, so not in 22.02 timeframe. 13:35:45 So for 22.02 I'd really like to get that released if it wasn't yet, but keeping 5.10.y as current. Edge is useless right on those ODROIDs. 13:35:46 rpardini: those images were recreated from repository 13:35:59 For 22.05 I promise to rework meson64 edge together with other meson64 maintainers and get it in good/better order, but for now armbian-next has priority. 13:36:10 <05fourheads> I have an N2+, maybe I can help 13:36:26 fourheads: you can pick up that bug perhaps? 13:36:37 rpardini I saw several patches about odroid in the kernel mailing list.don't they solve these problems? 13:36:52 We dont need to work hard on Edge, it is not meant to be stable. 13:37:03 IgorPec: yes, but from which branch? 13:37:24 <05fourheads> Sure, I can pick it up 13:37:27 adeepv: probably. that's why theres a big rework needed. 13:37:30 rpardini: packages were not built but used those from apt repo 13:37:49 this way i have updated a few images last week 13:38:45 ok, so imgs are new but old packages, so no, those PRs still havent seen light of day 13:39:08 so 22.02 would be the first to include them, *if we keep current to 5.10.y* 13:39:10 rpardini I also have an odroid-c4 if anything 13:39:35 if we bump current to 5.15.y, that work will disappear unreleased 13:40:04 why? we are moving 5.10.y to legacy? 13:40:26 no, I'm just making the point that 5.10.y should be kept as current. 13:40:28 rpardini In principle, I agree. the kernel can be postponed to 22.05 13:41:02 aha, well. we have the flexibility to do that 13:41:21 its your call. other families will have its own logic 13:41:32 there's a lot of meson64 boards that can run well with edge, a bit by luck 13:41:47 so I don't wanna impose. 13:42:18 IMHO legacy should always be considerd vendor/bsp kernel.... in general I hope that one day we can have stable adn old-stable LTS kernels... 5.10.y is a prime example 13:42:32 <08Tonymac32> Agreed 13:42:54 is there any point in having amlogic legacy? 13:42:57 exactly. for 22.05 we could remove vendor-legacy, and move 5.10.y to legacy, after reworking edge 5.16.y 13:43:11 + 13:43:24 I'm 99% ready to remove legacy. it's there for reference only, and the UHS fiasco 13:43:38 <08Tonymac32> In my opinion no, I never used it for GX(L), other than the pre-existing C2 stuff when I picked it up 13:43:50 <08Tonymac32> So if legacy went away I don't care in the least 13:44:12 yeah. i am asking speficic for amlogic. i agree that in some cases vendor kernel is needed 13:44:45 so conclusing is to keep current on 5.10.y for 22.02 13:44:52 ? 13:45:03 Aaaand he had enough :D 13:45:20 ok. so combo proposal is for 22.02 keep current as 5.10.y, edge as whatever; for 22.05 remove vendor legacy and move 5.10.y to legacy, and promote 5.15.y/5.16.y to current after rework 13:46:03 ok, nobody is agains i guess we can file it 13:46:14 IRC bounced me, sorry. 13:46:15 ok. so combo proposal is for 22.02 keep current as 5.10.y, edge as whatever; for 22.05 remove vendor legacy and move 5.10.y to legacy, and promote 5.15.y/5.16.y to current after rework. 13:46:38 #action Amlogic for 22.02 keep current as 5.10.y, edge as whatever; for 22.05 remove vendor legacy and move 5.10.y to legacy, and promote 5.15.y/5.16.y to current after rework. 13:46:48 ar-1061 is also to check 13:46:57 AR-1061 13:46:58 4AR-1061 6[Bug] "udev HDMI rules are causing flickering" reported by 3Igor Pecovnik at 2022-01-23. Status: To Do 13:47:19 this is some legacy hack from i don't know when 13:47:40 <05fourheads> Which Odroid Boards? 13:47:44 <05fourheads> All of them? 13:47:48 yes 13:47:49 ok, but on 5.15.y and thus for 22.05 timeframe...? 13:47:55 rpaedini ok. not very good for our devices, but quite acceptable. i'll have to revisit the patches for JetHub 5.10 again 13:48:12 *review ) 13:48:28 if edge stays on 5.15.y it should be safe enough 13:48:48 adeepv: I agree it's inconvenient, and appreciate the teamwork 13:49:12 hio. :) 13:50:10 yeah, i'm taking on all allwinner boards i can find with hardware SATA support. i'll probably take on a few without sata, but for now.. 13:50:13 finally #help if anyone would like to undertake that rework, I'd be glad to show around, since I'm mostly doing build system work. 13:50:33 my apologies for being late to the meeting. i didn't know we had meetings. :) 13:50:49 Yeah sorry I don't know all the ppls names to ping them. 13:51:02 that said, I guess I'm done ref 22.02. 13:51:05 https://forum.armbian.com/topic/19188-armbian-2202-pig-release-thread/ 13:51:34 #topic Marvell 13:51:35 fyi uboot is upped for amlogic to latest ... 13:52:06 IgorPec: exactly and looks great and might even solve some issues to facilitate rework. 13:52:27 heisath: ok, here we only have clearfogs . so you tell us ;) 13:52:28 _kernel_ rework mostly now, uboot is zeroed in. 13:52:35 Nothing big new or problematic here. No maintainer for espressobin. Helios4 and Clearfog are running good. I will test Lk5.15 and Lk5.16 13:52:37 <05fourheads> Somehow, I thought it was 8:30am (wishful thinking) - juri you are not alone. 13:53:12 upgrade current to 5.15.y would be nice if not too complicated 13:53:25 uboot has only bug with emmc on axg/sm1 chipset - 0001-HACK-mmc-meson-gx-limit-to-24MHz.patch fixes it 13:53:27 If we have little participants from east (china, australia etc.) we might move the meeting time to better suit usa and europe folks 13:54:15 BTW, i am more than half blocked, because of AR-1054. that's going to eat at least a week of hacker time for me.. which may take me a month to find. 13:54:16 4AR-1054 6[Epic] "eliminate the need to have root access to build the images." reported by 3Julia Longtin at 2022-01-15. Status: To Do 13:54:33 <05fourheads> Many times I have almost bought an espressobin - if it’s important, I can buy one and help out. 13:54:41 <05fourheads> But it seems to be less popularity 13:54:52 It is not popular and a pain in the butt. 13:54:52 juri_: we are getting to general section afterwardsd 13:55:10 Maybe you could get one and try it. Pali is doing lots of mainline work for it. 13:55:13 foruheads i have extra v5 i can send you 13:55:17 espressobin is not worth the trouble i think 13:55:32 Pali has done a lot. I have been following the mainline mailing lists. 13:55:42 yeah i think it might be usable _finally_ 13:55:54 yeah, we could cerainly probive something better now 13:56:32 i have one v4 (i think) still in the CI, but currently offline 13:56:39 Also he is somewhat responsive on the forum (unless Igor is involved) 13:57:26 yeah but he refruses to do PR's 13:57:31 because his hatred is that strong 13:57:42 historically i've ignored his stuff becuase of that 13:57:42 Yeah he's a mainline fellow, which is good somewhat. 13:57:46 fair 13:57:53 yeah i mean if someone wants to run with it i'm all for it 13:58:08 He's also trying to get lots of clearfog / helios4 patches into mvebu. 13:58:29 <05fourheads> When we say “mainline”, it seems we mean mainline kernel, right? 13:58:38 @fourheads yes 13:58:48 5.15 is fine for mvebu, I'll try to test 5.16 and then upgrade. 13:58:49 `git am` / `git format-patch` folks generally hate Github PRs, except for some very patient souls 13:59:06 #topic Rockchip 13:59:17 mainline == mainline or derived closely mainline, and not from a vendor kernel (there's some nuances that can be explained later) 13:59:32 status of u-boot on rockchip? 13:59:36 <05fourheads> Sure 14:01:15 <05fourheads> My RockPro64 just departed mainland China. Won’t have it in time to help with this release, maybe next one. 14:01:23 Looking at https://docs.google.com/spreadsheets/d/17O8X5FUxo8_567Xf0_V5ZcWC1IOcg5KSryTzKACegto/edit#gid=0, I see still no maintainer for rockpro64, is that correct? I thought I saw someone stepping up? 14:01:45 <05fourheads> I am willing to step up after I get my board. 🙂 14:01:49 AR-621 14:01:50 4AR-621 6[Task] "Enable SPI boot option for PineBook Pro" reported by 3Piotr Szczepanik at 2021-01-22. Status: To Do 14:02:08 @fourheads Maybe add yourself on that sheet I just posted the link 14:02:48 TRS-80: congratulations https://armbian.lane-fu.com/linx/eauz2kh7.tsv 14:02:55 u-boot v2021.07 is fine for 32 bit (both rk322x and rockchip families), but rk3288 tinkerboard has been left behind. Would like to move to 2022.01 soon for 32 bit, but can't test because have no tinkerboard 14:03:50 lanefu: lol, I was 'thinking about it' and then realized I am not sure I have time. Maybe I can start in secondary role, I dunno. 14:03:51 for tinkerboard we would like to keep usb flashing 14:03:57 <08Tonymac32> Jock this is because of the ums boot mode 14:04:04 <08Tonymac32> I am ok leaving that feature behind 14:04:08 Hmm, is there a maintainer for the orpi pc? 14:04:20 <05fourheads> Added myself TRS-80 14:04:21 <08Tonymac32> But Igor is not, which is fine 😉 14:04:24 FWIW, tilim actually PM me on forums offering to send hardware. 14:04:32 @fourheads thanks, cheers 14:04:41 on PINE64 forums I mean 14:04:42 ercatli see spreadsheet 14:04:51 let's see 14:05:05 ercatli--- we're on rockchip right now.. so follow-up after meeting 14:05:30 hmm, I see, there is a maintainer 14:05:45 Tonymac32: no problems with that, I guess rk3288 tinkerboard may require some u-boot config rework because of its older version if you want to upgrade 14:06:04 <05fourheads> Just be aware. I am still waiting for the Rockpro64 to arrive. 🙂 14:06:07 rockchip 3399 - usb type-c ? 14:07:20 for newer models - how is the status? anyone familiar 14:08:05 <05fourheads> Remind me when we get to OrangePI 14:08:11 <05fourheads> I just got a 3 LTS 14:08:24 <05fourheads> Which we don’t even have listed. 14:08:50 IgorPec: unfortunately I'm not, rockchip64/356x is out of my range 14:09:17 fourheads: feel free to add 14:09:47 here balbes and catallini report would be needed. i also don't know much 14:10:28 is Zaza here? 14:10:35 for rock3 rk 3568 is still wip, desktop mainline kernel is not working, usb3 not working...just basic stuff. 14:11:14 <08Tonymac32> On the boards I've worked on the type-c has full USB and DP alt mode working 14:11:21 <08Tonymac32> Rk3399 14:11:23 #info zaza: for rock3 rk 3568 is still wip, desktop mainline kernel is not working, usb3 not working...just basic stuff. 14:11:33 man i've never gotten that to work 14:11:36 ok. any outstanding task needed for 3399? 14:11:38 but i havent tried hard 14:12:04 using with desktop was only possible with legacy 4.19 14:12:07 the contencious talking about about some ethernet bugs on rock4b? cited in forum? 14:12:14 s/talking/talking point/ 14:12:15 lanefu meant to say: the contencious talking point about about some ethernet bugs on rock4b? cited in forum? 14:12:29 <08Tonymac32> Unfamiliar 14:12:32 i rebubbled that to radxa, but's chinese new year 14:12:37 and somehow manjaro and slack did the desktop work, but was laggy a lot 14:12:47 fyi olimex has some new RK3328 boards in case someone has a desire 14:13:05 * lanefu interested if they have 2 real nics 14:13:13 <08Tonymac32> + 14:13:26 i'll add that to forum once i got info 14:14:26 moving on? 14:14:40 #topic board other 14:14:58 i asuume here is odroid xu4 14:14:58 resuming for rock3a : is not so good for this february release 14:15:26 well, all the addings of uefi-x86 and uefi-arm64 and rpi4b from my side. those are wip. 14:15:44 and those as well. should we go out with those in 22.02? 14:16:11 AR-1048 14:16:12 4AR-1048 6[Bug] "Rpi kernel image is not updated on upgrade" reported by 3Igor Pecovnik at 2022-01-13. Status: To Do 14:16:14 * adeepv searching board with 3+ nics) 14:16:16 #action rock3a remains WIP for v20.02 14:16:22 do we have any maintainer smoke signals? I've seen you Igor touch them, but not much else. might be I'm not up-to-date 14:16:33 UEFI x86? Hmm, what about an MBR image? 14:16:38 yep, I've not tested any upgrades at all. 14:16:58 rpi seems in good shape, x86 i didn't test much, arm64 don't have hw 14:17:09 MBR is included for uefi-x86 via legacy i386 grub. system itself is 64-bit only though 14:17:48 I can't speak for the upgradeability of any of them, since that's not a scenario I encounter. 14:18:00 here - for arm64 - we should probably reach out for some parners 14:18:33 indeed. uefi-arm64 has been tested by locals here and I've reached out to SolidRun without success except for a pat in the back. 14:18:38 upgrading can be tested now, since kernels are available in repository 14:18:58 Tony an I have Phytium D2000's coming our way 14:19:11 so..... will get plenty of testing then 14:19:18 when is that planned? 14:19:20 yeah, Phytium should be the super smooth, and testing upgrades will be fun 14:19:24 i assume not for this release? 14:19:24 check's in hte mail 14:19:28 not this release 14:19:49 devices ariving feb-march 14:19:58 i would push rpi for this release, x86 is not that much relevant, arm64 we need hw 14:20:10 yeah. agree 14:20:15 i have a rpi4 now btw 14:20:23 rpi4b should be noted as experimental 14:20:30 like: might-not-upgrade 14:20:36 upgrade has to be fixed 14:20:43 I have an RPI 4 right now, too... 14:20:54 "upgrades" needs to be a whole discussion for later in meeting IMHO 14:21:00 its just that its not updating image on boot partition 14:21:02 ercaatli wanna bea mainter 14:21:04 yeah. I'd say if someone (not me and not Igor) steps up to fix upgrades then ok 14:21:15 but all of my zeros have ended up in the trash, actually, so weird... 14:21:31 AR-1048 seeking for help 14:21:32 4AR-1048 6[Bug] "Rpi kernel image is not updated on upgrade" reported by 3Igor Pecovnik at 2022-01-13. Status: To Do 14:22:18 that said I can point to a few spots I know that need addressing for upgradeability 14:22:55 anyone has a desire to look into this? He will get support from me and rpardini 14:23:05 Where is Cornelius, doesn't he like maintain his own RPi repo or something? 14:23:20 yes, he is around from time to time 14:23:26 he prefers to yell from the sidelines 14:23:30 Or am I thinking of someone else(?). 14:23:42 lanefu: I have been working on him, long term campaign. ;) 14:24:28 ok, lets try to fill that later. 14:24:31 yay 14:24:32 ahn also the sound thing, sorry 14:24:40 rpi4b vs userland audio 14:24:43 joekhoobyar: o/ 14:25:16 wow, this IRC client makes me feel like I'm in college again. It's 1995 all of a sudden 14:25:29 not a blocker for release, but again, I don't wanna get press saying "nice but no sound" as the best thing said 14:25:29 Any other different board things? Otherwise move to buildsystem. 14:25:51 #topic buildsystem enhancements 14:25:52 ok, I'll continue here. Would it help if I change my name to "fourheads" ? 14:26:09 just be yourself whatever head that is 14:26:14 joekhoobyar: not but would help if you stuck to agenda I guess 14:26:15 Dont care. Btw. did my #topics get ignored? 14:26:24 I did not see a confirmation by the bot. 14:26:37 for build system - rpardini 14:26:38 Heisath: bot caught it 14:26:46 ok good :D 14:26:47 i think it's silent if i remember 14:26:53 ok so build system is suffering massive refactor 14:26:54 Yeah for igor it was not 14:27:04 but it's on separate branch, and not even close to ready for 22.02 14:27:20 Heisath: yeah see channel topic.. it changed 14:27:33 I wouldn't mind helping on the refactor, rpardini - but I don't know what I don't know 14:27:35 smaller changes were - patching moved under series 14:27:42 #help 14:27:44 and it might not be worth readiing somebody else in 14:27:57 so its little bit better in sunxi, where we have a lot of them 14:27:59 up to you 14:28:15 * TRS-80 likes to follow PRs on GitHub, some times he even learns something 14:28:34 the plen for build system is that we merge rpardini changes then detach hardware layer into separate repo 14:28:46 after release 14:28:48 ok, so armbian-next branch will be PR'ed again after 22.02 release if all goes well 14:29:12 #action armbian-next transition part of roadmap imemdiately after release 14:29:45 also for those that might not beeing close much, there are new functionlities https://docs.armbian.com/Developer-Guide_Extensions/ 14:29:50 https://docs.armbian.com/Developer-Guide_Extensions-Hooks/ 14:30:25 thanks, @Igor, will read up 14:30:28 oh yes, _extensions_, that's already in for 22.02 14:30:42 Need to learn the build system. I am a baby 14:30:57 this information should be added to this release since it was never published 14:31:07 Yeah 14:31:11 and _juri wants that we get rid of su 14:31:19 I will invite all of you to play on armbian-next after finishing some things and rebasing master, which is a big work 14:31:23 since we are all here - do we have some sane way? 14:31:28 maybe add Jira with extension info, this way we get it to changelog automatically 14:31:53 there was no jira on extension topi AFAIK 14:32:08 exactly. Thats why I meant, create one now. 14:32:08 uh, it was AR-1009 I think 14:32:09 4AR-1009 6[Story] "Armbian Framework extensions and UEFI support" reported by 3Igor Pecovnik at 2021-11-28. Status: In Progress 14:32:38 ok, moving this in, cool 14:33:21 promise that _after_ armbian-next I will strictly stick to 1 thing per PR/AR 14:33:28 :-P 14:33:33 This is another task for really motivated people. Check through all the jira issues and make sure they are assigend to something, so they dont get lost. 14:33:37 * TRS-80 will believe it when he sees it :p 14:33:55 heisath: TRS-80 ?:) 14:34:07 I was joking with rpardini 14:34:21 oh you are volunteering me 14:34:25 yes ;) 14:34:26 heheh, you're right and it's funny :-D 14:34:27 It is about 244 items which are Todo or Backlogged. 14:34:38 yes this is suitable to my autism, perfect job for me 14:34:39 Heisath: file a longer version of that as a ticket, and i'll try to run with it. Jira is something i do, all day, almost every day. 14:34:56 this we should do together, but someone (trs) has to push on us 14:34:59 however I still was never able to auth to Jira, I will give it another try later today after meeting 14:35:06 Just need to check they are listed under some future release so we can find them and backlog them as neccessary. 14:35:07 internet bugs somehow, now I showed as zaza47 14:35:15 (i wear product owner / tech lead / scrum manager titles at $dayjob) 14:35:20 #action Cycle Jira issues which are not attached to a version. 14:35:54 juri_: You are welcome to it, esp as I still have yet to be able to log in to Jira. 14:36:02 Bt I will still try, anyway. 14:36:05 But 14:36:15 ok that's all from me I think. extensions in 22.02, armbian-next in 22.05 with previews before 14:36:18 for build script - this is all. i guess we can movbe to CI? 14:36:59 yeah 14:37:04 #topic CI / Infrastructure 14:37:17 juri_ yeah flex as hard as you want 14:37:18 Yeah my #topic does not work :D 14:37:24 #cat hearding 14:37:26 #topic CI 14:37:30 Ahn! 14:37:33