Armbian v21.05 (Jerboa) Release Thread


 Share

4 4

Recommended Posts

Release Planning: April 3rd. Meeting in IRC channel #armbian on freenode. Meeting starts at 2pm GMT.

(let me know if this is a bad date, because it is around easter holiday in Germany for example)

 

Code Freeze: 2021-04-19 (Monday April 19th)

Release Date: 2021-05-09 (Sunday May 9th)

Release Candidate: https://github.com/armbian/build/tree/v21.05.0-rc

Changelog: https://docs.armbian.com/Release_Changelog/#v2105-2021-05-09

Coordinator: @Heisath

 

The goal of this thread is to discuss testing, bugfixes, and the overall quality of the release. 

 

Open topics:

- complete desktop branch merge into master (this seems generally done, but might need fine tuning)

- enable 3D support (also done? Bugfixing)

- discuss support for desktops (IIRC it was planned to have a longer supported LTS desktop version, we need a maintainer for that, if it happens)

- check if remaining boards can / have been updated to LK5.10 (some were left out last release)

- check possible u-boot updates

- complete remaining Jira issues

- cycle and check board support status (espressobin for example needs a new maintainer (otherwise EOS) @Pali maybe?)

- late topics: 

- business meeting schedule

- kernel config changes on arm64

 

Release Planning Meeting Agenda:

Spoiler
  • check meeting attendees (if nick is not self explanatory, add your forum/Github handle. Just say hi or something)

  • present tasks, bugs or project you are working on. Jira should be open if not already.
  • cycle Jira backlog:
  • discuss task / bug (one at a time)
  • assign to person / release / tag
  • re-prioritise
  • cycle open issues and PR on build engine
  • board status update on download pages and build engine (wip, supported, eol)
  • choosing upcoming release officer
  • misc / open discussion

 

Please add developers and more topics below, I will then also add them here.

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

Link to post
Share on other sites

  • Igor pinned this topic
Donate and support the project!

On 3/8/2021 at 1:41 AM, Heisath said:

Please add developers and more topics below, I will then also add them here.

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


Hi! reminding everyone of meeting

 

On 3/8/2021 at 1:41 AM, Heisath said:

Release Planning: April 3rd. Meeting in IRC channel #armbian on freenode. Meeting starts at 2pm GMT.

(let me know if this is a bad date, because it is around easter holiday in Germany for example)

 

Link to post
Share on other sites

  • lanefu featured this topic

It was bad timing due to holiday but ... we manage to make it through. Comments and suggestions are welcome in this thread!

 

BTW. We also didn't find / set next meeting organiser yet. This time it was first time that also this responsibility was not mine (Thanks to @Heisath) and I really want that this becomes a tradition. Responsibility of officer should cycle so we all get familiar. Its to call people, run meeting script and surrounding activities. Log is made semi automatically by @Werner's IRC-fu. It's not hard, can also be lead by someone that is not a developer and (s)he gets a full technical support.

 

 

Link to post
Share on other sites

@those who didnt make it: 

 

No problem, just check the meeting log http://meeting.armbian.de/ , the irc chat log (irc.armbian.com/logs) and the Jira issues for the next release (https://armbian.atlassian.net/secure/RapidBoard.jspa?projectKey=AR&rapidView=2)

 

@all:

 

For the next weeks, remember to try and fix Jira issues (also mark them as done), review open PRs and issues on github. And try to get your work done before the codefreeze 2021-04-19 (Monday April 19th). :)

 

@Igor:

Quote

It was bad timing due to holiday but ... we manage to make it through. Comments and suggestions are welcome in this thread!

Wouldn't say so. I asked about the holiday thing in first post, also with note to possible reschedule. People could've said something beforehand ;)

 

@the new release dude:

Show yourself! It's easy and a good way to help the project without  needing to get all technical.

Link to post
Share on other sites

Code freeze has happened.

 

I have branched an rc version (https://github.com/armbian/build/tree/v21.05.0-rc ) please send bugfixes here (additionally to the master branch).

 

Also the version of the master branch has been set to 21.08.0-trunk.

 

Please check the remaining Jira and Github PRs to see if anything in Jira needs closing (will be used to generate the changelog). 

 

Testing and Bugfixing will be until beginning of May.

 

Kind regards,

Heisath

Link to post
Share on other sites

Current situation on our test farm - except from Odroid C4 and Lepotato boot issue - power cycle is needed, things are fairly stable:

Spoiler

[ o.k. ] 0. Trying [ 11:50:02 - 50.253 ]
[ o.k. ] Orange Pi Zero Plus 2 Linux 5.10.30-sunxi U-Boot 2021.04-armbian  focal nightly [ 11:50:16 - 50.253 Uptime: 5 min ]
[ o.k. ] 1. Trying [ 11:50:16 - 50.215 ]
[ o.k. ] Orange Pi Lite 2 Linux 5.10.30-sunxi64 U-Boot 2021.04-armbian  focal nightly [ 11:50:24 - 50.215 Uptime: 7 min ]
[ o.k. ] 2. Trying [ 11:50:24 - 30.100 ]
[ o.k. ] Cubietruck Linux 5.10.30-sunxi U-Boot 2020.10-armbian  focal nightly [ 11:50:44 - 30.100 Uptime: 7 min ]
[ o.k. ] 3. Trying [ 11:50:45 - 30.101 ]
[ o.k. ] Orange Pi Zero Plus Linux 5.10.30-sunxi64 U-Boot 2021.04-armbian  focal nightly [ 11:50:55 - 30.101 Uptime: 6 min ]
[ o.k. ] 4. Trying [ 11:50:55 - 30.102 ]
[ o.k. ] Odroid XU4 Linux 5.4.112-odroidxu4 U-Boot 2017.05-armbian  focal nightly [ 11:51:05 - 30.102 Uptime:  1:55 ]
[ o.k. ] 5. Trying [ 11:51:05 - 30.103 ]
[ o.k. ] Orange Pi One Linux 5.10.30-sunxi U-Boot 2021.04-armbian  focal nightly [ 11:51:18 - 30.103 Uptime: 8 min ]
[ o.k. ] 6. Trying [ 11:51:18 - 30.104 ]
[ o.k. ] RockPro 64 Linux 5.10.31-rockchip64 U-Boot SPL 2020.10-armbian  focal nightly [ 11:51:27 - 30.104 Uptime:  1:55 ]
[ o.k. ] 7. Trying [ 11:51:27 - 30.105 ]
[ o.k. ] Cubieboard Linux 5.10.30-sunxi U-Boot 2020.10-armbian  focal nightly [ 11:51:48 - 30.105 Uptime:  1:55 ]
[ o.k. ] 8. Trying [ 11:51:48 - 30.106 ]
[ o.k. ] Banana Pi Pro Linux 5.10.30-sunxi U-Boot 2021.04-armbian  focal nightly [ 11:52:10 - 30.106 Uptime:  1:56 ]
[ o.k. ] 9. Trying [ 11:52:10 - 30.107 ]
[ o.k. ] Orange Pi Win Linux 5.10.30-sunxi64 U-Boot 2021.04-armbian  focal nightly [ 11:52:20 - 30.107 Uptime:  1:56 ]
[ o.k. ] 10. Trying [ 11:52:20 - 30.108 ]
[ o.k. ] Orange Pi Prime Linux 5.10.30-sunxi64 U-Boot 2021.04-armbian  focal nightly [ 11:52:28 - 30.108 Uptime: 35 min ]
[ o.k. ] 11. Trying [ 11:52:29 - 30.111 ]
[ o.k. ] Espressobin Linux 5.10.31-mvebu64  focal nightly [ 11:52:44 - 30.111 Uptime:  1:57 ]
[ o.k. ] 12. Trying [ 11:52:44 - 30.112 ]
[ o.k. ] Orange Pi+ 2E Linux 5.10.30-sunxi U-Boot 2021.04-armbian  focal nightly [ 11:52:57 - 30.112 Uptime: 39 min ]
[ o.k. ] 13. Trying [ 11:52:57 - 30.113 ]
[ o.k. ] Orange Pi 3 Linux 5.10.30-sunxi64 U-Boot 2021.04-armbian  focal nightly [ 11:53:06 - 30.113 Uptime:  1:57 ]
[ o.k. ] 14. Trying [ 11:53:06 - 30.116 ]
[ o.k. ] Le potato Linux 5.10.31-meson64  focal nightly [ 11:53:16 - 30.116 Uptime: 10 min ]
[ o.k. ] 15. Trying [ 11:53:16 - 30.117 ]
[ o.k. ] Rockpi 4B Linux 5.10.31-rockchip64  hirsute nightly [ 11:53:26 - 30.117 Uptime: 10 min ]
[ o.k. ] 16. Trying [ 11:53:26 - 30.118 ]
[ o.k. ] Cubox i2eX/i4 Linux 5.10.31-imx6 U-Boot 2018.01-armbian  focal nightly [ 11:53:45 - 30.118 Uptime:  1:58 ]
[ o.k. ] 17. Trying [ 11:53:45 - 30.120 ]
[ o.k. ] Nanopi R2S Linux 5.10.31-rockchip64  focal nightly [ 11:53:54 - 30.120 Uptime: 8 min ]
[ o.k. ] 18. Trying [ 11:53:54 - 30.121 ]
[ o.k. ] NanoPi R4S Linux 5.10.31-rockchip64  focal nightly [ 11:54:04 - 30.121 Uptime: 8 min ]
[ o.k. ] 19. Trying [ 11:54:04 - 30.123 ]
[ o.k. ] Jetson Nano Linux 5.10.31-jetson-nano U-Boot 2021.01-armbian  focal nightly [ 11:54:13 - 30.123 Uptime:  1:58 ]
[ o.k. ] 20. Trying [ 11:54:13 - 30.125 ]
[ o.k. ] OrangePi 4 Linux 5.10.31-rockchip64  focal nightly [ 11:54:21 - 30.125 Uptime: 11 min ]
[ o.k. ] 21. Trying [ 11:54:21 - 30.132 ]
[ o.k. ] NanoPi R1 Linux 5.10.30-sunxi U-Boot 2021.04-armbian  focal nightly [ 11:54:38 - 30.132 Uptime: 9 min ]
[ o.k. ] 22. Trying [ 11:54:38 - 30.140 ]
[ o.k. ] NanoPi Neo 2 Black Linux 5.10.30-sunxi64 U-Boot 2021.04-armbian  focal nightly [ 11:54:46 - 30.140 Uptime: 44 min ]
[ o.k. ] 23. Trying [ 11:54:46 - 30.141 ]
[ o.k. ] ZeroPi Linux 5.10.30-sunxi U-Boot 2021.04-armbian  focal nightly [ 11:55:00 - 30.141 Uptime:  1:59 ]
[ o.k. ] 24. Trying [ 11:55:00 - 30.148 ]
[ o.k. ] Tinkerboard Linux 5.10.31-rockchip U-Boot 2018.11-armbian  focal nightly [ 11:55:07 - 30.148 Uptime: 10 min ]
[ o.k. ] 25. Trying [ 11:55:07 - 30.150 ]
[ o.k. ] Orange Pi R1 Linux 5.10.29-sunxi U-Boot 2021.04-armbian  focal nightly [ 11:55:23 - 30.150 Uptime: 10 min ]
[ o.k. ] 26. Trying [ 11:55:23 - 30.169 ]
[ o.k. ] Clearfog Pro Linux 5.11.8-mvebu U-Boot 2018.01-armbian  focal nightly [ 11:55:33 - 30.169 Uptime:  2:00 ]
[ o.k. ] 27. Trying [ 11:55:33 - 30.170 ]
[ o.k. ] Udoo Linux 5.10.31-imx6 U-Boot 2017.11-armbian  focal nightly [ 11:55:51 - 30.170 Uptime:  2:00 ]
[ o.k. ] 28. Trying [ 11:55:51 - 30.217 ]
[ o.k. ] Odroid N2 Linux 5.10.31-meson64  focal nightly [ 11:55:58 - 30.217 Uptime:  2:00 ]
[ o.k. ] 29. Trying [ 11:55:58 - 30.218 ]
[ o.k. ] NanoPC T4 Linux 5.10.31-rockchip64  focal nightly [ 11:56:07 - 30.218 Uptime:  1:48 ]
[ o.k. ] 30. Trying [ 11:56:07 - 30.219 ]
[ o.k. ] Rockpi E Linux 5.10.31-rockchip64  focal nightly [ 11:56:19 - 30.219 Uptime: 13 min ]
[ o.k. ] 31. Trying [ 11:56:19 - 30.227 ]
[ o.k. ] NanoPi Neo 3 Linux 5.10.31-rockchip64  buster nightly [ 11:56:28 - 30.227 Uptime:  2:00 ]
[ o.k. ] 32. Trying [ 11:56:28 - 30.228 ]
[ o.k. ] Pine H64 Linux 5.10.30-sunxi64 U-Boot 2021.04-armbian  focal nightly [ 11:56:36 - 30.228 Uptime: 13 min ]
[ o.k. ] 33. Trying [ 11:56:36 - 30.236 ]
[ o.k. ] Odroid C2 Linux 5.10.31-meson64 U-Boot 2021.04-armbian  focal nightly [ 11:56:46 - 30.236 Uptime:  2:01 ]
[ o.k. ] 34. Trying [ 11:56:46 - 30.240 ]
[ o.k. ] Odroid C4 Linux 5.10.31-meson64  focal nightly [ 11:56:54 - 30.240 Uptime:  2:01 ]
[ o.k. ] 35. Trying [ 11:56:54 - 30.246 ]
[ o.k. ] NanoPi M4 Linux 5.10.31-rockchip64  focal nightly [ 11:57:02 - 30.246 Uptime:  2:01 ]
[ o.k. ] 36. Trying [ 11:57:02 - 30.254 ]
[ o.k. ] Orange Pi Zero Linux 5.10.30-sunxi U-Boot 2021.04-armbian  focal stable [ 11:57:17 - 30.254 Uptime: 12 min ]

 


 


 

Link to post
Share on other sites

So planned release candidate period is almost over.  Not much feedback here... 

 

Any comments from the devs / testers on state?  Igors testfarm looks good.

 

Also please tell me if any of the commits on master (since rc) need to be included in this release (as they are bugfixes):
https://github.com/armbian/build/compare/v21.05.0-rc...master

 

@tparys @piter75 @Igor @lanefu @Werner @Rich Neese @Paolo @redchenjs (dont know the forum tags)

Link to post
Share on other sites

28 minutes ago, Heisath said:

So planned release candidate period is almost over.  Not much feedback here... 

 

We probably need to make this more visible - people does not understand its value. Outside developers group - this is yet another topic. I would rely and improve automatic testing methods in any case.

 

32 minutes ago, Heisath said:

Igors testfarm looks good.


Amlogic reboot issues are not yet ironed out - worse case this will be noted in release documentation.

 

34 minutes ago, Heisath said:

Also please tell me if any of the commits on master (since rc) need to be included in this release (as they are bugfixes):


Master contains more or less just bug fixes or irrelevant things such as additional board(s). I would say we just merge. No need for cherry-picking.

Link to post
Share on other sites

On 5/3/2021 at 8:32 AM, Heisath said:

Can you please check the Jira issues that are still "In Progress", or can I assume they are all not done? Or are some expected to be closed in May?


Done. Those which I am unsure if they are fully done, were simply moved forward, to next release. I also usually check if there is something important in the commit log, but fall out of Jira. This is added manually at this stage. If nothing, we can proceed. I will start with a build process hopefully this weekend. Then https://www.armbian.com/newsflash/armbian-20-11-tamandua/ is needed for this release and the most important: what to change to improve, automatise and simplify for the future?

Link to post
Share on other sites

All images has been built and synching is in progress ... I did few manual checks (Odroid N2 focal xfce and Banana M2+ CLI buster) and they both are working as expected. If a critical problems is found and we have a quick fix, we can fix and rebuild a single image at this point. If problems is minor -> a bug in Jira.

 

@HeisathNeed any help in making release docs? Anything else we are missing?
 

Link to post
Share on other sites

Nah, all good from here. I'll try to do the release this sunday. Might hop in the IRC if I need assistance. Release on sunday evening is good IMHO because if something critical goes wrong, we can fix on monday.

Link to post
Share on other sites

So release has been done, marked in Jira, created on github, updated the docs, and created a post in announcements.

 

Only things left from list are:

- Point Armbian build system to new release (done already I guess?)

- Celebrate, have fun!

Link to post
Share on other sites

vor 1 Stunde schrieb Heisath:

Seems ok to me? 

Well - than its odd!

I tried 21.02.3 which works perfect. Anything is clear and understandable.

And it was the first linux image, that boots right from emmc (written by balena with usb-adapter)

 

vor 1 Stunde schrieb Heisath:

Have you tried just typing in a new root pw and pressing enter?

No I haven't.

If current behaviour is ok for you, than 21.05.1 is not for me.

I'm fine with 21.02.3 !

Link to post
Share on other sites

31 minutes ago, tony013 said:

If current behaviour is ok for you, than 21.05.1 is not for me.

 

This cosmetic and harmless issue is present for year(s) on different images and I haven't spot much complains about. Also - if it bothers you, welcome to fix it https://docs.armbian.com/Process_Contribute/

 

I would highly suggest you to use most recent images since they should have less bugs, at least those important ones.

Link to post
Share on other sites

3 hours ago, tony013 said:

No I haven't.

If current behaviour is ok for you, than 21.05.1 is not for me.

I'm fine with 21.02.3 !

 

Yeah we ususlly ssh in on first boot so wouldn't see that.  But yes its only cosmetic and you could just press enter and proceed as normal

 

If you are particular about your system and avoiding changes you may want to freeze the kernel on your 21.02 install via armbian-config 

 

Add jira task https://armbian.atlassian.net/browse/AR-743

Link to post
Share on other sites

vor 33 Minuten schrieb lanefu:

If you are particular about your system and avoiding changes you may want to freeze the kernel on your 21.02 install via armbian-config 

I thought I had found my solution, but unfortunately that is not the case.

 

I tried boot from usb-media - but that's no solution either. It doesn't boot, if the boot drive was plugged into a different usb-slot. What a mess!

Link to post
Share on other sites

Hello folks! What is your preferred way to receive trouble reports? I have actually two issues with the recently release on a Cubieboard2. I do know that this is officially not supported. So your answer might well be, that you are not in favor of receiving any reports. Thanks!

Link to post
Share on other sites

1 hour ago, tony013 said:

I thought I had found my solution, but unfortunately that is not the case.

 

I don't understand what problem you're trying to solve.  Based on the picture you shared, you just need to press enter and a fresh prompt will draw.

 

1 hour ago, tony013 said:

What a mess!

 

Comments like this are insulting to me and probably other devs as well.

Link to post
Share on other sites

44 minutes ago, cw73 said:

Hello folks! What is your preferred way to receive trouble reports? I have actually two issues with the recently release on a Cubieboard2. I do know that this is officially not supported. So your answer might well be, that you are not in favor of receiving any reports. Thanks!

 

Hey great question.  Just share your issue in the peer support thread or the subforum that is relevant to the hardware you're using

Link to post
Share on other sites

  • lanefu unpinned and unfeatured this topic

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

4 4