I would very much like my pull request in https://issues.apache.org/jira/browse/ZOOKEEPER-3739 to be merged in 3.6.1 and newer, because it helps ensure newer java APIs don't leak into pull requests/patches when developing stuff to contribute using a newer JDK, by leveraging the "release" flag of newer JDKs. However, in order to do so, it needs to remove the use of an internal com.sun API which is not supported in newer JDKs. I would like it included, because it makes it easier for me (and others using newer JDKs) to contribute.
The patch is currently pending additional reviewers. On Thu, Mar 19, 2020 at 11:17 AM Patrick Hunt <ph...@apache.org> wrote: > Great idea, thanks Enrico! > > Patrick > > On Thu, Mar 19, 2020 at 4:58 AM Enrico Olivelli <eolive...@gmail.com> > wrote: > > > Hi folks, > > after a couple of weeks after the release of 3.6.0 we are seeing a few > > blocker issues related to the upgrade from 3.5. > > > > There is already a good list of issues already ported to 3.6 and a few > > pending PRs that fix problems reported by users. > > > > You can find the list here, I have already did some clean up and left > > comments to "reporters" in order to remove a few issues that are > > tagged 3.6.1 but they don't have an active contributor working on it. > > I have also created 3.6.2 release in order to ease moving those issues > > > > > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20ZOOKEEPER%20AND%20fixVersion%20%3D%203.6.1%20ORDER%20BY%20resolution%20DESC > > > > My proposal: > > - commit pending blocker patches related to the upgrade > > - start a release within a couple of weeks, in the beginning of April > > > > I volunteer to do the release, this way I can finish the "new release > > procedure" based on the Maven Release Plugin > > > > Enrico > > >