Mailing-List: contact dev-help@yetus.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@yetus.apache.org
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
Subject: Re: [VOTE] Apache Yetus 0.2.0-RC1
From: Allen Wittenauer <allenwittenauer@yahoo.com.INVALID>
In-Reply-To: 
 <CAEhbgS+BghREU_Ej4MvsKEE3v2VzWjSYViMD=myaSzSJRZmSbQ@mail.gmail.com>
Date: Thu, 3 Mar 2016 08:44:27 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <E30C77C6-08C1-40C1-B28A-3BBC2B06CF9E@yahoo.com>
References: <FE2BFEF4-85EE-4717-8F6A-6668289490FF@altiscale.com>
 <D2FB2959.3C59A%cnauroth@hortonworks.com>
 <CAEhbgS+BghREU_Ej4MvsKEE3v2VzWjSYViMD=myaSzSJRZmSbQ@mail.gmail.com>
To: dev@yetus.apache.org


> On Mar 3, 2016, at 8:14 AM, Kengo Seki <sekikn@gmail.com> wrote:
>=20
> * I found some "2015"s in LICENSE and NOTICE. Should we update them =
with
> "2016" before release?

	The one in NOTICE is definitely wrong.  The only entries in =
LICENSE I see are for copyrights related to 3rd party works which I =
don=E2=80=99t think have been updated this year.  I=E2=80=99d hate to =
have to cancel this RC based upon this, but it=E2=80=99s probably the =
correct thing to do. :(

> * I tried "ASF required checks" No.4, but I couldn't find the =
0.2.0-RC1
> branch (does Allen's comment[2] mean it?).

	I'd consider this is a bug in the documentation.   The =E2=80=9Cho=
w to release=E2=80=9D docs create the branch based upon the issue #, =
doesn't set a temporary tag either, and only shares the git commit hash. =
The paragraph before step 4 says:

"You SHOULD make sure the source release artifact corresponds to the =
referenced commit hash in the [VOTE] thread. [=E2=80=A6] Our eventual =
release tag is how we=E2=80=99ll provide long term provinence =
information for our downstream users.=E2=80=9D

	It acknowledges that we=E2=80=99ll eventually have a release =
tag, but we don=E2=80=99t yet.  So I think the branch checkout should =
probably be replaced with a hash checkout.

> I used the YETUS-318 branch
> instead, but I got an unexpected result:

	FWIW, the YETUS-318 branch should definitely correspond to the =
given git hash in the vote thread.

> [sekikn@mobile 0.2.0-RC1]$ diff -r yetus-0.2.0-RC1-tag
> yetus-0.2.0-src_unpack/yetus-0.2.0
> Only in yetus-0.2.0-RC1-tag: .git

	Understandable.

> Only in yetus-0.2.0-src_unpack/yetus-0.2.0: CHANGES.md
> Only in yetus-0.2.0-src_unpack/yetus-0.2.0: RELEASENOTES.md

	IMO, I think this is a good thing to have in the source tar =
ball.

I=E2=80=99ll need to dig deeper into the rest.

> diff: yetus-0.2.0-RC1-tag/asf-site-src/source/documentation/0.1.0: No =
such
> file or directory