public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "Maxim Yu. Osipov" <mosipov@ilbers.de>
To: isar-users@googlegroups.com
Subject: Re: [PATCH v2 1/1] changelog: v0.7-rc1
Date: Fri, 15 Mar 2019 05:50:13 +0100	[thread overview]
Message-ID: <275b0da2-0fd9-72ac-88d0-3143d83832bb@ilbers.de> (raw)
In-Reply-To: <20190311171704.23523-2-mosipov@ilbers.de>

On 3/11/19 6:17 PM, Maxim Yu. Osipov wrote:

Applied to the 'next'.

> Signed-off-by: Maxim Yu. Osipov <mosipov@ilbers.de>

> ---
>   ChangeLog                   | 27 +++++++++++++++++++++++++++
>   RECIPE-API-CHANGELOG.md     |  4 ++--
>   Supported_Configurations.md |  2 +-
>   3 files changed, 30 insertions(+), 3 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..e5f3150 100644
> --- a/RECIPE-API-CHANGELOG.md
> +++ b/RECIPE-API-CHANGELOG.md
> @@ -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
> 


-- 
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-15  4:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-11 17:17 [PATCH v2 0/1] Isar v0.7 Release Candidate 1 Maxim Yu. Osipov
2019-03-11 17:17 ` [PATCH v2 1/1] changelog: v0.7-rc1 Maxim Yu. Osipov
2019-03-15  4:50   ` Maxim Yu. Osipov [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=275b0da2-0fd9-72ac-88d0-3143d83832bb@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