Mailing-List: contact dev-help@edgent.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@edgent.apache.org
From: Dale LaBossiere <dml.apache@gmail.com>
Content-Type: multipart/alternative;
 boundary="Apple-Mail=_3318C33C-2761-47DA-9019-65DAD72D0C4C"
Mime-Version: 1.0 (Mac OS X Mail 10.1 \(3251\))
Subject: Re: [DISCUSS] validating Apache Edgent (Incubating) 1.2.0 RC1
Date: Sat, 9 Dec 2017 14:38:53 -0500
References: <70323EB9-C271-4F7F-B1E7-2A2A83F1A7F4@c-ware.de>
 <5878DC61-B179-4754-A7ED-329851674265@gmail.com>
 <21769CF9-90A4-4E57-931F-D91F61C4274E@c-ware.de>
 <DE372311-170C-492B-8851-587E65B2B50D@c-ware.de>
 <D0C0298D-3D64-44CF-BEC0-01383348E871@gmail.com>
 <8A4ABDC8-AC52-4A25-BF28-606CCC04D245@c-ware.de>
 <4E5E17FD-1054-4343-B285-7FA2590F4CEE@gmail.com>
 <DB5PR05MB1608D130DFDD46424F1834F2A2320@DB5PR05MB1608.eurprd05.prod.outlook.com>
 <D69A856B-35F9-4800-B3F6-031C46AC9BE2@gmail.com>
 <DB5PR05MB160838174E63E7A6971E4801A2320@DB5PR05MB1608.eurprd05.prod.outlook.com>
 <36A0EEEC-C657-4786-9C94-F994577D1D7C@gmail.com>
 <DB5PR05MB1608A77918DDF0777E0C278FA2320@DB5PR05MB1608.eurprd05.prod.outlook.com>
 <CB324F40-DD77-4470-B0CD-2F9E4CD5D5AC@gmail.com>
 <F2F74CFC-5B23-4443-B62F-1FDA7878B5F4@c-ware.de>
 <48ACCCEC-7D32-4EE2-AD15-4D1E533E8EB8@gmail.com>
To: dev@edgent.apache.org
In-Reply-To: <48ACCCEC-7D32-4EE2-AD15-4D1E533E8EB8@gmail.com>
Message-Id: <43AEE252-9CCD-466F-A3E5-EA3C5F316372@gmail.com>
archived-at: Sat, 09 Dec 2017 19:39:03 -0000

--Apple-Mail=_3318C33C-2761-47DA-9019-65DAD72D0C4C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

I was able to successfully perform almost all of the validation on the =
source bundle that I wanted to:
- basically followed the non-RM, non-binary items in [6]
    downloaded, checked signatures/sums, checked identical tar.gz / zip =
contents
    verified LICENSE, NOTICE, DISCLAIMER, RELEASE_NOTES, README
    build/tested via README

I will run the manual kafka tests to verify those look good.

But there are a couple of things...

- I wanted to review more detailed test result status from my manual =
release build/test validation
 (e.g., what was run / what was skipped as noted in [6]) but  =E2=80=9C./m=
vnw clean install site:site site:stage=E2=80=9D
 failed, complaining that the source tree wasn=E2=80=99t a git repo.

- It=E2=80=99s unclear to me if the *exact jar/war bits* staged in nexus =
have been tested or not.
  I suspect they have been tested, hence there=E2=80=99s nothing missing =
or broken, but want to verify.  Chris, can you elaborate on that please?
  If they have been tested as part the release process so far, is there =
a test results and code coverage reports
  that one can review?

[6] =
https://cwiki.apache.org/confluence/display/EDGENT/Staged+RC+Validation =
<https://cwiki.apache.org/confluence/display/EDGENT/Staged+RC+Validation>

=E2=80=94 Dale=

--Apple-Mail=_3318C33C-2761-47DA-9019-65DAD72D0C4C--