On 17/06/2019 15:58, Gary Gregory wrote: > The version in the release notes at the top still says "1.1" instead of > "1.1.1".
My understanding was they referred to 1.1.x (i.e. all of the 1.1 releases) so the version number was appropriate. > It seems to me that 1.2 would be more appropriate since we upgraded both > the Java and OS requirements. No we didn't. See the changelog. The Java and OS requirements are the same for 1.1.1 as they are for 1.1.0. Mark > > Gary > > On Mon, Jun 17, 2019, 08:13 Mark Thomas <ma...@apache.org> wrote: > >> It has been ~18 months since the last Commons Daemon release. After the >> recent flurry of activity, I think we are ready for a release. >> >> Notable changes include: >> - Improved JRE/JDK detection to support increased range of both JVM >> versions and vendors. >> - Procrun. Change the default service from LocalSystem to >> 'NT Authority\LocalService' >> >> The full set of changes is in the changelog >> >> 1.1.1 can be obtained from (r34537): >> https://dist.apache.org/repos/dist/dev/commons/daemon/ >> >> The git tag is: >> https://github.com/apache/commons-daemon/commits/COMMONS_DAEMON_1_1_1 >> 4319f482e1ff6ea7655e1377120750fd6ecc3810 >> <https://github.com/apache/commons-daemon/commits/COMMONS_DAEMON_1_1_14319f482e1ff6ea7655e1377120750fd6ecc3810> >> >> The Maven Staging repo is: >> https://repository.apache.org/content/repositories/orgapachecommons-1441/ >> >> The Windows binaries have been signed by the Symantec code signing service. >> >> >> >> [ ] Approved - go ahead and release Commons Daemon 1.1.1 >> [ ] Broken - do not release because... >> >> --------------------------------------------------------------------- >> 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
