On 16 July 2018 at 15:42, Gary Gregory <garydgreg...@gmail.com> wrote: > On Mon, Jul 16, 2018 at 8:00 AM Rob Tompkins <chtom...@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-unsubscr...@commons.apache.org >> For additional commands, e-mail: dev-h...@commons.apache.org >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
