public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "Maxim Yu. Osipov" <mosipov@ilbers.de>
To: isar-users <isar-users@googlegroups.com>
Subject: [ANNOUNCE] Upcoming ISAR v.07 Release Candidate #2
Date: Tue, 19 Mar 2019 11:40:03 +0100	[thread overview]
Message-ID: <1c3e076d-b653-72ec-a291-da2d92134c73@ilbers.de> (raw)

Hello everybody,

I'm going to make the ISAR v.07 release candidate #2.

I've summarized the patch series that were applied since rc1 or put on 
hold (with the reason).

If I missed some of your patches or you have some urgent topics which 
are the subject to delay the upcoming release please let me know.


The following patch series (bug fixes) were applied since rc1:
==============================================================
* meta: refactored flock usage by Claudius Heine
* Python refactoring by Harald Seiler and Claudius Heine
* linux-custom: fix for kernels without module by Cedric Hombourger
* buildchroot: do not assume group of "builder" to be "builder" by 
Henning Schild
* u-boot-custom: Add git as build dependency by Jan Kiszka
* dpkg: acquire a read (shared) locks while building packages by Cedric 
Hombourger
* debianize: use date of the most recent file instead of "now" by Cedric 
Hombourger
* changelog: v0.7-rc1  by Maxim Osipov
* Separation of isar images per machine by Maxim Osipov


The following patch series were put on hold:
============================================

* Refactor ext4 image class by Claudius Heine.

Reason: I don't want to drop support for jessie (at least for v.07 release)

* Fix usage of additional apt keys and repos by Andreas Reichel

Reason: v5 series (sent on 18/3/2019) has problems with CI.
v6 series received several minutes ago needs extensive testing.

* Merge patch and unpack tasks and buildchroot: Allow downgrades when 
installing packages by Jan Kiszka

Reason: People on the mailing list have issues regarding these two patches

* wic-img: switch over to use the template.bbclass mechanism by Claudius 
Heine

Reason: postponed after the release as this is not a bug fix.

Regards,
Maxim.

-- 
Maxim Osipov
ilbers GmbH
Maria-Merian-Str. 8
85521 Ottobrunn
Germany
+49 (151) 6517 6917
mosipov@ilbers.de
http://ilbers.de/
Commercial register Munich, HRB 214197
General Manager: Baurzhan Ismagulov

                 reply	other threads:[~2019-03-19 10:40 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=1c3e076d-b653-72ec-a291-da2d92134c73@ilbers.de \
    --to=mosipov@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