Fully agree. It makes sense to promote on master and prepare a release. I would like to do a new pass on Karaf 4.2.x support as well before the release.
I think we could make a Shiro 2.0.0.RC1 just to do a complete pass before a GA. Regards JB On 05/01/2019 20:18, Francois Papon wrote: > Hi all, > > According to Git history, we can see a branch about the next major > release 2.0.0 with big changes on api design :) > > This work was made 3 years ago and I would like to know if we can move > forward on it and include other interesting changes like: > > * upgrade minimum JDK version to 8 > * support JDK 9/10/11 > * better OSGi support (unique package declaration per bundle, review > maven-bundle-plugin declaration) > * improve Apache Karaf support (upgrade to Karaf 4.2.2, review > features.xml, add itests for Karaf) > * upgrade dependencies and plugins version > > It would be interesting to move this branch on master and create a > maintenance branch for 1.4.x after we had released the 1.4.0 (actually > on 1.4.0-RC2 and their is 3 issues left to cut the release). > > Thoughts? > > -- > François Papon > [email protected] > -- Jean-Baptiste Onofré [email protected] http://blog.nanthrax.net Talend - http://www.talend.com
