Armbian 22.02 (Pig) Release Thread


Heisath
 Share

3 3

Recommended Posts

Release Candidate Code Freeze Date: 2022-02-14

Release Planning Meeting Date:  2022-01-29 14:00 UTC+1 

Release Planning Meeting Location: Armbian IRC
Release Date: 2022-02-28

Release Branch Link: https://github.com/armbian/build/tree/v22.02

Release Changelog:

Spoiler

Release notes - Armbian - Version 22.02

 

Bug

AR-1101 DRM patch is failing on Rockchip

AR-1079 Ubuntu archive redirector is not providing best service

AR-1077 Fix RPi4 userland audio

AR-1069 First login doesn't pick up correct shell

AR-1065 Twitter forum registration is not working

AR-1063 X86 desktop images are not enabled in CI

AR-1062 When selecting repository install u-boot might not be flashed

AR-1055 Aptly repository seems to be out of business

AR-1048 Rpi kernel image is not updated on upgrade

AR-1043 linux-firmware repository change branch from "master" to "main"

AR-973 Helios64 boot building is failing after update to 2021.10

AR-871 Debian SID broken wallpaper

 

Story

AR-1074 Switch all CURRENT to 5.15.y and EDGE to 5.16.y

AR-1009 Armbian Framework extensions and UEFI support

 

Task

AR-1100 Support for Orange Pi R1 Plus LTS, Drivers for YT8531 and other Motorcomm chips. Linux-5.10y and Linux-5.15y.

AR-1084 Enable 3D support on Debian desktop

AR-1078 Add additional forum plugins and adjust settings

AR-1068 Add gnome-system-monitor to Focal and Jammy

AR-1049 Add ZFS that supports kernel 5.15.y

AR-1044 Improve Raspberry Pi support

AR-1041 JetHome: fix brcm (AP6255) firmware links

AR-1040 Refactor armbian-bsp-cli package creation

AR-931 Using Docker image for building kernels

AR-893 Cleanup rockchip64 u-boot scenarios

AR-757 Adding Raspberry Pi

AR-586 Implement fan controller for Nanopi M2V2

 

 

Release Coordinator: @Heisath and hopefully some new person on the team :)

 

Already creating this release topic for 22.02, to discuss upcoming changes, no longer maintained boards and help new people get into the release / maintain flow.

 

Current steps:

- Refine supported/WIP/CSC/etc. board status

- Update maintainer list

- Onboard new maintainers / contributors

- Move Jira issues to new release

- Select release name 

 

@Igor @Werner @TonyMac32 @martinayotte @piter75 @ning @Myy @balbes150 @sfx2000 @ebin-dev @chwe  @gprovost @aprayoga @lanefu @5kft @JMCC @going @jeanrhum @dolphs @jock @belfastraven @TRS-80 @Bozza @Rich Neese @sgjava @Mangix @tony013  @rpardini

 

Pls. ping developers I forgot :) 

Link to post
Share on other sites

  • Heisath changed the title to Armbian 22.02 (No name yet) Release Thread
Armbian is a community driven open source project. Do you like to contribute your code?

  • lanefu featured and pinned this topic
On 11/1/2021 at 6:24 PM, Heisath said:

- Refine supported/WIP/CSC/etc. board status

- Update maintainer list

- Onboard new maintainers / contributors

- Move Jira issues to new release

- Select release name 

 

Some of this is already in the works and should be done soon.

 

We also need to prepare and present communication strategy for new maintainers - basically just review what is expected within maintainer role:

https://forum.armbian.com/staffapplications/application/8-single-board-computer-maintainer/

and how we would like that things run. And take their suggestions. We want that those people feel good but also have healthy expectations.

 

And second meeting - technical one as we did in the past. Or we join all in one? Important is that new people (@yang is responsible for keeping the list updated) are invited there.

Link to post
Share on other sites

I would still go on with the February release, we skipped last one, lets get this one done.

 

Am targeting 2022-01-29 (Saturday, 29 of January 2022) for release meeting, and then about 4 weeks later 2022-02-25 (Friday, 25 of February 2022) for actual release. 

Release meeting earlier than 2022-01-25 is not possible from my calendar.

 

 

Link to post
Share on other sites

  • lanefu changed the title to Armbian 22.02 (Pig) Release Thread

Improved testing on hardware - its attached to nightly builds and currently needs to be run manually:

 

badge.svg

 

  • connects to the device via SSH as root (ssh key must be there)
  • runs apt update + upgrade
  • reboots
  • waits 3 minutes that machine is back
  • true or false
  • power cycle the board in case of false (where we have power control)

 

Currently 38 boards are attached, but its very simple to add more of them.

Link to post
Share on other sites

57 минут назад, Igor сказал:

Currently 38 boards are attached, but its very simple to add more of them.

what about remote boards? I can connect jethub h1/d1 with power/reset/console remote control

Link to post
Share on other sites

Fixed some UX troubles on the download pages, examples:  https://www.armbian.com/banana-pi-m2-plus/ https://www.armbian.com/rpi4b/ https://www.armbian.com/odroid-hc4/

 

- download list is now completely automated, pulling from build config files https://github.com/armbian/build/blob/master/config/targets.conf

- added option to advertise recommended targets at download pages https://armbian.atlassian.net/browse/AR-1057 by setting a property in a targets.conf

- label supported / not supported for kernel is no more. instead label for CLI / Desktop / minimal

- added "Closed bootloader" property

- improved FAQ

- enabled WIP builds for: RPi4, UEFI arm & x86

 

Link to post
Share on other sites

Reminder! The release meeting is happening this saturday 14:00 UTC+1 (which is 13:00 UTC or 8 am EST or 2 pm CET or 5 am PST (sorry california dudes) or 9 pm CST).

 

I will look through the Jira issues remaining today. Would be great if you could check them too and add the ones you have finished (or are planning to include in 22.02) to the release.

 

@Igor @Werner @TonyMac32 @martinayotte @piter75 @ning @Myy @balbes150 @sfx2000 @ebin-dev @chwe @gprovost @aprayoga @lanefu @5kft @JMCC @going @jeanrhum @dolphs @jock @belfastraven @TRS-80 @Bozza @Rich Neese @sgjava @Mangix @tony013 @rpardini @yang @adeepn

Link to post
Share on other sites

12 hours ago, lanefu said:

anymore thoughts about group mention plugin for forum?


https://armbian.atlassian.net/browse/AR-1078 (one more is also interesting)
Added, but it doesn't work properly. I have tried by enabling it for all, but now it's enabled that administrators can call administrators. Dunno why its not working - support topic: https://invisioncommunity.com/forums/topic/439130-group-mention

Link to post
Share on other sites

2 hours ago, Igor said:


https://armbian.atlassian.net/browse/AR-1078 (one more is also interesting)
Added, but it doesn't work properly. I have tried by enabling it for all, but now it's enabled that administrators can call administrators. Dunno why its not working - support topic: https://invisioncommunity.com/forums/topic/439130-group-mention

I'll look into

Link to post
Share on other sites

19 minutes ago, Igor said:

here we need a list of all board maintainers

 

From Forum Name Cross Reference section of (new) Board Maintainers page in our documentation (and then a little multiple-cursors action in Emacs), et voila:  :D

 

@antondeveloper, @balbes150, @catalinii, @Heisath, @Igor, @yang, @joekhoobyar, @krachlatte, @LucasM, @piter75, @NicoD, @RadxaYuntian, @seclorum, @teknoid, @TonyMac32, @TRS-80, @ZazaBr

 

Hmm, although simply pasting a list of @user1, @user2, etc. did not activate the mention.  Had to go through manually and still start to type and then click on them.  :/

 

Edited by TRS-80
edit list of @user1, @user2 into actual mentions
Link to post
Share on other sites

I want to suggest making a change to getting the source code for the kernel. Switch from using BRANCH to TAG. This will allow you to fix the source code used and synchronize it with patches, configuration and other settings. Now, at any start of the build, the source code is automatically synchronized and it is constantly updated to the latest available version, which causes a number of problems (destruction of some patches used, appearance \ removal of options in the kernel, driver changes). When using TAG, we can control switching (transition) to a new version of the kernel, i.e. this process becomes fully controlled and the version change is performed manually by the maintainers in their configuration files. But there is a drawback, you need to change the process of deleting the no longer used version of the kernel source code, there are different solutions that can be discussed.

 

https://github.com/150balbes/build/blob/armbian-tv/config/sources/families/media.conf#L67

Link to post
Share on other sites

09.02.2022 в 15:31, balbes150 сказал:

. But there is a drawback, you need to change the process of deleting the no longer used version of the kernel source code, there are different solutions that can be discussed.

The solution has been present for a long time. See how it happens for sunxi:

https://github.com/armbian/build/blob/3c1dde938cbea0bf0fee17049ad61cda74f1ee17/config/sources/families/include/sunxi64_common.inc#L78

https://github.com/armbian/build/blob/3c1dde938cbea0bf0fee17049ad61cda74f1ee17/lib/general.sh#L294

The function creates a shallow clone of the original linux-stable target branch. And can add a branch from another repository of the same version, but with additional commits. Switching is very simple. The function is tested and works for sunxi. If you set the key KERNELSWITCHOBJ=v5.15.7, it will extract this tag, but it will continue to update. Everything happens without changing the directory. The directory is always named as version 5.15.

I already have a solution for a full replacement for the fetch_from_repo function, but it has not yet been fully tested.

Link to post
Share on other sites

  • Igor unpinned this topic
 Share

3 3