From: Anton Mikanovich <amikan@ilbers.de>
To: isar-users@googlegroups.com
Subject: Re: Upcoming Isar release (0.8)
Date: Tue, 18 Jan 2022 12:53:02 +0300 [thread overview]
Message-ID: <0e9d5ddb-1382-6f53-241f-d89a0e7de9d3@ilbers.de> (raw)
In-Reply-To: <20211215090527.GO22100@yssyq.m.ilbers.de>
15.12.2021 12:05, Baurzhan Ismagulov wrote:
> Hello all,
>
> we would like to release the next version of Isar (0.8) in January.
>
> This includes the following steps:
>
> - Postpone new features and potentially unstable changes till after the release
>
> - Merge bug fixes
>
> - Update distros, test on hardware, prioritize CI issue analysis
>
> - Update docs
>
> With kind regards,
> Baurzhan.
>
Here are the list of patchsets supposed to be included in the v0.8 on
top of the current next (33b5aa65):
[PATCH v2,0/1] ci: make vm_start logs readable by all users
[PATCH v2,0/1] Fix conflicting names of image manifest and dpkg_status
[PATCH] image: Add machine into mount points path
[PATCH] u-boot-script: Drop runtime dependency on a kernel
[PATCH v4 00/10] Update testsuite targets
[PATCH v2 0/2] Actualize iMX6 targets
[PATCH v2,0/6] Update rpi targets to bullseye
[PATCH v3 0/8] Update Isar documentation (TBD)
+v0.8-rc2 and v0.8 patchsets with changelogs and tags updates
Please feel free to declare anything else need to be included.
prev parent reply other threads:[~2022-01-18 9:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-15 9:05 Baurzhan Ismagulov
2022-01-18 9:53 ` Anton Mikanovich [this message]
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=0e9d5ddb-1382-6f53-241f-d89a0e7de9d3@ilbers.de \
--to=amikan@ilbers.de \
--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