Mailing-List: contact general-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: general@incubator.apache.org
Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.1 \(3445.4.7\))
Subject: Re: [VOTE] Release of Apache BatchEE 0.5-incubating
From: Mark Struberg <struberg@yahoo.de.INVALID>
In-Reply-To: <CAOGo0Vbgj6hH-BL0U45P9cnxp19CaiGijP297i3z48kgUsyNBQ@mail.gmail.com>
Date: Sun, 10 Dec 2017 11:35:04 +0100
Cc: BatchEE Dev BatchEE Dev <dev@batchee.incubator.apache.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <0888E995-CB5B-4C7E-B6F4-9D468D9C82AB@yahoo.de>
References: <50A3C9E0-BAA0-4A33-8B2D-F6FCF054AE31@apache.org>
 <CAOGo0VYK37SoTy1OrrjBAqj-=3Fp0T6p67ZxB0U8ZL=0DZ6H3A@mail.gmail.com>
 <D4C94F24-C255-4826-82E4-AF94E58B88DA@yahoo.de>
 <CAOGo0Vbn6_kt2JEtwRV0FRH4MyadMGC799EDv6s8_qijrzAchg@mail.gmail.com>
 <7C3F2FD2-A364-4ADC-8C48-FA602C7803FD@yahoo.de>
 <CAOGo0Vbgj6hH-BL0U45P9cnxp19CaiGijP297i3z48kgUsyNBQ@mail.gmail.com>
To: general@incubator.apache.org
archived-at: Sun, 10 Dec 2017 10:35:18 -0000


> If you put them under /dev/ for the vote, that makes it easier for the
> reviewer to see what is actually intended for the release area.

Yes and no. Where do we get this zip from?=20
The answer is: from repository.apache.org. Because all this is set up in =
the ASF own apache-parent pom.xml!

You are indeed right in pointing out that the original vote mail should =
have added the sha1 of the source zip to vote on.
Let's fix that:
b51aebefc01e94f96df3d1a6664835524b855cf7

But you are wrong by assuming that with dist/dev all would be perfect. =
Indeed, a SVN location is not worth much either if you don't know the =
_exact_ SVN revision!
And this is missing in almost all votes as well.=20

By forcing dist/dev you basically render the staging area of =
repository.apache.org useless. You agree?
And one more drawback is that ditching a failed release from SVN will =
_not_ free the occupied storage.
That might or might not be an issue. But it still would be a change to =
what we do in many TLPs since many years.

In my personal opinion the dist/dev is a fine solution if the project =
does not leverage a fully automated release build.
But for projects which use the maven-release-plugin doing a release is =
as easy as mvn release:prepare + mvn release:perform.
All the rest is done automatically, including the deployment to a =
staging area at repository.apache.org.
=20
Forcing dist/dev for those projects would imo be more or less a step =
back to deploying release candidates to people.a.o as we did a decade =
ago.=20
There was a good reason why we did get rid of that, you probably =
remember...

Don't get me wrong: it's always good to review and discuss our release =
process.
What Reinhard did with the BatchEE release is really identical to what =
we do in many TLPs.=20
What we really need to fix is the part with the sha1 (even better would =
be sha256 though) as this is the only 100% way to ensure the VOTE is =
really on the right source zip.=20
Is this documented in the incubator release howto already?

LieGrue,
strub

> Am 07.12.2017 um 15:01 schrieb sebb <sebbaz@gmail.com>:
>=20
> On 7 December 2017 at 10:22, Mark Struberg <struberg@yahoo.de.invalid> =
wrote:
>> Hi Sebb!
>>=20
>> commits got pushed to the ASF repo
>> https://github.com/apache/incubator-batchee/commits/master
>>=20
>> And we clarified the dist question with Infra.
>> All is fine as repository.apache.org is ASF owned and operated =
territory.
>> The only thing which we must make sure is that the source zip get's =
copied over to dist.a.o once the VOTE did succeed.
>=20
> If you put them under /dev/ for the vote, that makes it easier for the
> reviewer to see what is actually intended for the release area.
>=20
>> And we have to ofc make sure that it is really the same as voted =
upon. We ensure this via the sha1.
>=20
> I don't understand how that can work, given the content of the VOTE =
mail.
> Note that the Nexus repo URLs are transient and not version controlled =
AFAICT.
> Nor are they unique as the numbers will eventually wrap.
>=20
> Try to use the SHA1 of any of the files in the previous release to
> prove that the file is the one that was voted on.
>=20
> For example, under
> www.apache.org/dist/incubator/batchee/0.4-incubating/
> we have
> batchee-0.4-incubating-source-release.zip.sha1
> which contains
> 05535de5554b598356f27bdb475853675b80b8b4
>=20
> The release vote is here:
> =
https://lists.apache.org/thread.html/fc112978fe7682a95189f9d14567ddef23bd2=
fc860bbce89903bf5c9@%3Cgeneral.incubator.apache.org%3E
>=20
> How do you prove that the source zip is the one that was voted on?
>=20
>> txs and LieGrue,
>> strub
>>=20
>>=20
>>=20
>>> Am 06.12.2017 um 23:16 schrieb sebb <sebbaz@gmail.com>:
>>>=20
>>> On 6 December 2017 at 17:06, Mark Struberg =
<struberg@yahoo.de.invalid> wrote:
>>>> No sebb, the tag does NOT need to be owned by the PPMC.
>>>> We just have to make sure that the tag gets moved over to ASF =
_AFTER_ the vote is closed.
>>>> That's how GIT works and that's how we work with GIT since many =
years at the ASF.
>>>>=20
>>>>> The source must be released through the ASF mirror system,
>>>>> The source must be released through the ASF mirror system,
>>>>> The staging area for that is here:
>>>>=20
>>>> That's also ONLY valid for AFTER the vote!
>>>=20
>>> No, the /dev/ area is the normal location for RCs
>>>=20
>>>> So once the VOTE passes we will copy it over.
>>>=20
>>> Once the vote passes you SVN copy/move /dev/ to /release/
>>>=20
>>>> Again: we handle it that way in TLPs and many podlings since MANY =
years.
>>>=20
>>> There have been changes over the years, including the introduction =
of
>>> dist.apache.org.
>>>=20
>>> The point is to provide a staged copy of the release candidate under
>>> /dev/ that reviewers can check.
>>>=20
>>> Ideally also provide the SVN revision of the folder in the vote =
email.
>>>=20
>>> This then provides traceability from the vote to the /release/
>>> (assuming SVN is used to move/copy the files from /dev/ to =
/release/).
>>>=20
>>>>> The KEYS file must be under
>>>>> https://www.apache.org/dist/incubator/batchee/ as must the sigs =
and hashes.
>>>>=20
>>>> again AFTER the VOTE!
>>>=20
>>> The KEYS file can be updated at any time to include the RM's key.
>>> It's vital that it is in place ready in case the vote succeeds.
>>> So it makes sense to reference it in the VOTE email.
>>>=20
>>>> for the record: Romain and my votes are IPMC binding ones.
>>>=20
>>>> txs and LieGrue,
>>>> strub
>>>>=20
>>>>=20
>>>>> Am 06.12.2017 um 16:41 schrieb sebb <sebbaz@gmail.com>:
>>>>>=20
>>>>> On 6 December 2017 at 08:08, Reinhard Sandtner =
<rsandtner@apache.org> wrote:
>>>>>> Hey incubator PMCs,
>>>>>>=20
>>>>>> The Apache BatchEE community has voted and approved the proposal =
to release Apache BatchEE 0.5-incubating.
>>>>>> Apache BatchEE is a JBatch implementation (JSR-352) which =
provides many enhancements and extensions.
>>>>>>=20
>>>>>> You may find the VOTE thread here:
>>>>>> =
https://lists.apache.org/thread.html/50c023e02cebcb61bc61aa2ea6112d366b1db=
a0db04c045b7c1b415b@%3Cdev.batchee.apache.org%3E =
<http://mail-archives.apache.org/mod_mbox/batchee-dev/201712.mbox/%3C50176=
7C2-1220-41F1-A8F9-73330969DAF1@apache.org%3E>
>>>>>>=20
>>>>>> the RESULT VOTE thread can be found here:
>>>>>> =
https://lists.apache.org/thread.html/6d05ea8439167e15d720d318c9c2845fbd134=
ae2967321e3b7540386@%3Cdev.batchee.apache.org%3E =
<https://lists.apache.org/thread.html/6d05ea8439167e15d720d318c9c2845fbd13=
4ae2967321e3b7540386@%3Cdev.batchee.apache.org%3E>
>>>>>>=20
>>>>>> For information about the contents of this release, see:
>>>>>> =
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=3D1231492=
4&version=3D12334679 =
<https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=3D123149=
24&version=3D12334679>
>>>>>>=20
>>>>>> The tag is available on my github fork
>>>>>> =
https://github.com/rsandtner/incubator-batchee/tree/batchee-0.5-incubating=
 =
<https://github.com/rsandtner/incubator-batchee/tree/batchee-0.5-incubatin=
g>
>>>>>=20
>>>>> That does not seem right.
>>>>> Tags need to be permanent and 'owned' by the (P)PMC
>>>>>=20
>>>>>> Staging Repo is here:
>>>>>> =
https://repository.apache.org/content/repositories/orgapachebatchee-1005<h=
ttps://repository.apache.org/content/repositories/orgapachebatchee-1005>
>>>>>=20
>>>>> That is only the Maven staging area.
>>>>>=20
>>>>> The source must be released through the ASF mirror system,
>>>>>=20
>>>>> The staging area for that is here:
>>>>>=20
>>>>> https://dist.apache.org/repos/dist/dev/incubator/batchee/
>>>>>=20
>>>>> [If the vote succeeds, the files can be moved here:
>>>>> https://dist.apache.org/repos/dist/release/incubator/batchee/]
>>>>>=20
>>>>>> Sources can be found here:
>>>>>> =
https://repository.apache.org/content/repositories/orgapachebatchee-1005/o=
rg/apache/batchee/batchee/0.5-incubating/batchee-0.5-incubating-source-rel=
ease.zip<https://repository.apache.org/content/repositories/orgapachebatch=
ee-1005/org/apache/batchee/batchee/0.5-incubating/batchee-0.5-incubating-s=
ource-release.zip>
>>>>>>=20
>>>>>> Release artifacts are singed with the KEY:
>>>>>> =
https://github.com/apache/incubator-batchee/blob/master/KEYS<https://githu=
b.com/apache/incubator-batchee/blob/master/KEYS>
>>>>>=20
>>>>> The KEYS file must be under
>>>>> https://www.apache.org/dist/incubator/batchee/ as must the sigs =
and
>>>>> hashes.
>>>>>=20
>>>>>=20
>>>>>> The vote is open for 72 hours
>>>>>=20
>>>>> At least 72 hours.
>>>>>=20
>>>>>> [ ] +1 batchEE -> coolShipIt()
>>>>>> [ ] +0 don=E2=80=99t care
>>>>>> [ ] -1 do not release because=E2=80=A6
>>>>>>=20
>>>>>> thanks, lg
>>>>>> reini
>>>>>=20
>>>>> =
---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>=20
>>>>=20
>>>> =
---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>=20
>>>=20
>>> =
---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> For additional commands, e-mail: general-help@incubator.apache.org
>>=20
>>=20
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>=20
>=20
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org