commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sebb <seb...@gmail.com>
Subject Re: [release-plugin] RCs easier to create than validate
Date Mon, 16 Jul 2018 16:54:18 GMT
On 16 July 2018 at 15:42, Gary Gregory <garydgregory@gmail.com> wrote:
> On Mon, Jul 16, 2018 at 8:00 AM Rob Tompkins <chtompki@gmail.com> wrote:
>
>> Just wanted to make note of this. But, automating validation is mildly
>> sketchy IMO.
>>
>
> There is a checklist called "Things To Look For When Inspecting A Release
> Candidate" on https://commons.apache.org/releases/prepare.html
>
> but it is pretty lame IMO. We should list how to:
> - Verify ASC files
> - Verify SHA files

Check that hashes agree with vote mail

> - Run and check Apache RAT
> - Run and check Clirr
> - Run and check Japicmp
> - Check a site
> - Run a build
>
> What else?

Check that source artifact contents agrees with tag.
Check that source and binary artifacts contain appropriate N&L files
at top-level or under META-INF
Check that binary artifacts don't have spurious contents (e.g. files
left in workspace or unexpected 3rd party jars)
Check that RELEASE NOTE has the correct version number
Likewise CHANGES if present.

> Gary
>
>
>> -Rob
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Mime
View raw message