+1 (non-binding) So far I've check:
* Source release matches with source repository. * Signatures and digests. * Checked headers, LICENSE and NOTICE files. * Build (OpenJDK 1.8.0_144 with Maven 3.5.0). On Thu, Nov 16, 2017 at 6:06 AM, Mark Thomas <ma...@apache.org> wrote: > On 15/11/17 12:35, Mark Thomas wrote: > > <snip/> > > > The proposed 1.1.0 release based on RC3 is: > > [ ] Broken - do not release because... > > [X] Approved - go ahead and release as 1.1.0 > > Windows with Tomcat 7.0.82 > Tested by replacing the Windows binaries with those from Commons Daemon > 1.1.0. > - Digital signatures are valid (Symantec code signing) > - Passed simple smoke test running on Java 6 > - Configuring Java 9 specific options didn't prevent running on Java 6 > (as expected) > - Java 9 options used when running on Java 9 (needed to remove > endorsedDirs setting - as expected) > > Windows with Tomcat trunk > - Passed simple smoke test running on Java 8 > > Linux with Tomcat trunk > - Warnings compiling jsvc > - same warnings as with 1.0.15 but now a few more due to DAEMON-377 > fix (not a release blocker in my view) > - Runs under Java 8 > - Runs under Java 9 > > Packaging > - Detailed checks for RC 2 didn't turn up any issues > - RC3 spot checks of > - commons-daemon-1.1.0-sources.jar > - commons-daemon-1.1.0-native-src.tar.gz > - commons-daemon-1.1.0.jar > No issues found > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > >
