public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "Maxim Yu. Osipov" <mosipov@ilbers.de>
To: Jan Kiszka <jan.kiszka@siemens.com>, isar-users@googlegroups.com
Subject: Re: [PATCH 1/1] changelog: v0.7-rc1
Date: Tue, 5 Mar 2019 07:28:50 +0100	[thread overview]
Message-ID: <5a690032-0b72-a41c-60dc-927d64dc5f28@ilbers.de> (raw)
In-Reply-To: <2b55cf09-625e-9508-0ffc-6056d9ea7681@siemens.com>

On 3/4/19 8:51 AM, Jan Kiszka wrote:
> On 01.03.19 23:06, Maxim Yu. Osipov wrote:
>> Signed-off-by: Maxim Yu. Osipov <mosipov@ilbers.de>
>> ---
>>   ChangeLog                   | 27 +++++++++++++++++++++++++++
>>   RECIPE-API-CHANGELOG.md     |  6 +++---
>>   Supported_Configurations.md |  2 +-
>>   3 files changed, 31 insertions(+), 4 deletions(-)
>>   create mode 100644 ChangeLog
>>
>> diff --git a/ChangeLog b/ChangeLog
>> new file mode 100644
>> index 0000000..1be4e8c
>> --- /dev/null
>> +++ b/ChangeLog
>> @@ -0,0 +1,27 @@
>> +Release v0.7
>> +
>> + * Improved CI scripts
>> + * Added setting of root (encrypted) password
>> + * Added support for UBI file system images
>> + * Added support of "apt://" in SRC_URI to fetch/unpack/rebuild an 
>> upstream package
>> + * Renamed example-hello to hello-isar to avoid collisions with 
>> Debian hello
>> + * Moved debian distro conf files from meta-isar to meta
>> + * Added support of tar.gz images
>> + * Debian "raw" packages are built using the whole dpkg-buildpackage 
>> workflow
>> + * Supported host system >= stretch
>> + * bitbake updated to the 19dee675
>> + * Added LeMaker HiKey board support
>> + * Added Terasic DE0-Nano-SoC support
>> + * Added option to create local apt repo caching upstream Debian 
>> packages
>> +
>> +Release v0.6
>> +
>> + * Migration to deboostrap from multistrap as later is deprecated
>> + * WIC support is integrated
>> + * Added cross compilation support
>> + * Added SDK root filesystem creation
>> + * Added Debian buster support
>> + * Dropped wheezy support
>> + * Added Banana Pi support
>> +
>> +Release v0.5
>> diff --git a/RECIPE-API-CHANGELOG.md b/RECIPE-API-CHANGELOG.md
>> index 197ce99..741ab22 100644
>> --- a/RECIPE-API-CHANGELOG.md
>> +++ b/RECIPE-API-CHANGELOG.md
>> @@ -1,7 +1,7 @@
>>   Recipe API Changelog
>>   ====================
>> -Baseline: Release v0.5
>> +Baseline: Release v0.7
> 
> This is wrong, the baseline for the first changes noted for v0.6 remain 
> v0.5.


Oh, Sorry.

BTW, do you think that this order (from the oldest to the latest) is 
natural (I refer to your commit a601b9f)?

All ChangeLogs I've seen before list entries in the opposite order.



Thanks,
Maxim.


>>   Changes in v0.6
>>   ---------------
>> @@ -73,8 +73,8 @@ you now have to set `KERNEL_NAME = "foo"` in order 
>> to select that kernel.
>>   Alternatively, a recipe with a different naming scheme can set
>>   `KERNEL_NAME_PROVIDED = "foo"` in order to match as well.
>> -Upcoming changes (v0.7)
>> ------------------------
>> +Changes in v0.7
>> +---------------
>>   ### dpkg-raw recipes build method changed
>> diff --git a/Supported_Configurations.md b/Supported_Configurations.md
>> index e36f14a..8767f38 100644
>> --- a/Supported_Configurations.md
>> +++ b/Supported_Configurations.md
>> @@ -1,7 +1,7 @@
>>   Supported Configurations
>>   ========================
>> -Release next
>> +Release v0.7
>>   ------------
>>   ### Host System : debian-jessie-amd64
>>
> 
> Jan
> 


-- 
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-05  6:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-01 22:06 [PATCH 0/1] Isar v0.7 Release Candidate 1 Maxim Yu. Osipov
2019-03-01 22:06 ` [PATCH 1/1] changelog: v0.7-rc1 Maxim Yu. Osipov
2019-03-04  7:51   ` Jan Kiszka
2019-03-05  6:28     ` Maxim Yu. Osipov [this message]
2019-03-05  6:51       ` Jan Kiszka

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=5a690032-0b72-a41c-60dc-927d64dc5f28@ilbers.de \
    --to=mosipov@ilbers.de \
    --cc=isar-users@googlegroups.com \
    --cc=jan.kiszka@siemens.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