From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users@googlegroups.com
Subject: Isar 0.8
Date: Mon, 31 Jan 2022 17:19:56 +0100 [thread overview]
Message-ID: <YfgMLJLI1GnmVP4f@ilbers.de> (raw)
Hello all,
we've tagged v0.8.
Changes:
* Add Debian Sid Ports support
* Add Debian Bookworm support
* Add Debian Bullseye support
* Drop Debian Jessie support
* Add Ubuntu Focal support
* Add Raspberry Pi OS support
* Add RISC-V architecture support
* Add MIPSel architecture support
* Add STM32MP15x eval board target
* Add NanoPi NEO board target
* Add HiFive Unleashed board target
* Add qemuriscv64 virtual target
* Add iMX6 SabreLite target
* Add Raspberry Pi 1B, 1B+, 2B, 3 targets
* Update BitBake version to 1.46.2 release
* Update WIC to the revision b85a09ea4
* Update U-Boot version to 2020.10
* Update linux-mainline version to 5.4.70
* Migrate CI to Avocado Framework
* Split CI on fast and full builds
* Add Sstate (Shared State) Cache support
* Add Ccache support
* Add deb-src caching support
* Add UEFI boot with systemd-boot
* Add CPIO image type (initramfs like filesystem) generation support
* Add VMWare/Virtualbox image generation support
* Add containerized filesystem and sdk generation support
* Add initramfs generation support
* Add multiple image types support
* Add Linux Kernel Selftests recipe
* Add prebuilt debs injecting support
* Add devshell and devshell_nodep targets
* Add git-buildpackage support
* Add buildstats generation and pybootchartgui
* Force running GPG-agent on demand
* Allow clear-text passwords for users
* Add compat architecture support via multiarch
* Add image versioning
* Add build dependencies defining support for debianization
* Add multiple DTBs deploying support
* Add BB_NO_NETWORK option
* Migrate to deb.debian.org in apt sources.list
* Add AUTOREV support for SRCREV
* Add support for patches in sub-directories
* Add rootfs postprocessing
* Allow downgrades when installing packages
* Deprecate isar-image
With kind regards,
Baurzhan.
reply other threads:[~2022-01-31 16:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=YfgMLJLI1GnmVP4f@ilbers.de \
--to=ibr@radix50.net \
--cc=isar-users@googlegroups.com \
/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