From mboxrd@z Thu Jan  1 00:00:00 1970
Return-path: <rauc-bounces@pengutronix.de>
Received: from mail-wr1-x42b.google.com ([2a00:1450:4864:20::42b])
 by metis.ext.pengutronix.de with esmtps
 (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92)
 (envelope-from <mcampbell@izotope.com>) id 1jgv8U-0005QD-R3
 for rauc@pengutronix.de; Thu, 04 Jun 2020 21:02:44 +0200
Received: by mail-wr1-x42b.google.com with SMTP id x13so7298550wrv.4
 for <rauc@pengutronix.de>; Thu, 04 Jun 2020 12:02:42 -0700 (PDT)
MIME-Version: 1.0
From: Matt Campbell <mcampbell@izotope.com>
Date: Thu, 4 Jun 2020 15:02:30 -0400
Message-ID: <CAMDowVVbSDM+BAJoksBTqN7oy6frsm0Oo16wB8Wg5Uupe0Q_LQ@mail.gmail.com>
Subject: [RAUC] Backwards/forwards compatibility of bundle format
List-Id: RAUC Project - Discussion List <rauc.pengutronix.de>
List-Unsubscribe: <http://metis.pengutronix.de/cgi-bin/mailman/options/rauc>, 
 <mailto:rauc-request@pengutronix.de?subject=unsubscribe>
List-Archive: <http://metis.pengutronix.de/pipermail/rauc/>
List-Post: <mailto:rauc@pengutronix.de>
List-Help: <mailto:rauc-request@pengutronix.de?subject=help>
List-Subscribe: <http://metis.pengutronix.de/cgi-bin/mailman/listinfo/rauc>,
 <mailto:rauc-request@pengutronix.de?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1501386244=="
Errors-To: rauc-bounces@pengutronix.de
Sender: "RAUC" <rauc-bounces@pengutronix.de>
To: rauc@pengutronix.de

--===============1501386244==
Content-Type: multipart/alternative; boundary="000000000000f3cb5b05a746c998"

--000000000000f3cb5b05a746c998
Content-Type: text/plain; charset="UTF-8"

Hi All,

I'm looking into RAUC for a product, and I was wondering if there are any
project goals around the stability of the RAUC bundle format. Specifically,
it would be great if all future versions of the rauc binary was compatible
will all previous bundle formats, and also that all older versions of the
binary can install future created bundles. Obviously that's a big ask, but
it'd be great to know what to expect of RAUC in the future. Even a rough
idea of how compatibility will  play out will help me greatly in evaluating
RAUC.

Best,
~Matt
-- 
Matthew Campbell
Senior Embedded Systems Engineer
mcampbell@izotope.com

iZotope, Inc.
www.izotope.com

--000000000000f3cb5b05a746c998
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi All,<div><br></div><div>I&#39;m looking into RAUC for a=
 product, and I was wondering if there are any project goals around the sta=
bility of the RAUC bundle format. Specifically, it would be great if all fu=
ture versions of the rauc binary was compatible will all previous bundle fo=
rmats, and also that all older versions of the binary can install future cr=
eated bundles. Obviously that&#39;s a big=C2=A0ask, but it&#39;d be great t=
o know what to expect of RAUC in the future. Even a rough idea of how compa=
tibility=C2=A0will=C2=A0 play out will help me greatly in evaluating RAUC.<=
/div><div><br></div><div>Best,</div><div>~Matt<br>-- <br><div dir=3D"ltr" c=
lass=3D"gmail_signature" data-smartmail=3D"gmail_signature"><div dir=3D"ltr=
">Matthew Campbell<div>Senior Embedded Systems Engineer</div><div><a href=
=3D"mailto:mcampbell@izotope.com" target=3D"_blank">mcampbell@izotope.com</=
a></div><div><br></div><div>iZotope, Inc.</div><div><a href=3D"http://www.i=
zotope.com" target=3D"_blank">www.izotope.com</a></div></div></div></div></=
div>

--000000000000f3cb5b05a746c998--


--===============1501386244==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
RAUC mailing list

--===============1501386244==--