There might be a lot more to consider here since this would be a major release. Are there breaking API changes we want to make? Are there deprecated APIs we want to drop?
I see a lot of errors fly by when I do a local build on Windows but these do not seem to fail the build which is odd. It seems to me that this project has not been released in a long time, so there should be some consideration to taking advantage of the version of Java the component is now sitting on. I think I saw an animal sniffer setting set to Java 15? How does that make sense? To make a long story short, we should not be in a rush to release a major new version just for the sake of creating a release. Maybe that would be better in the 3.x context, I'm not sure. Gary On Thu, Dec 24, 2020, 07:11 Lukasz Lenart <lukaszlen...@apache.org> wrote: > Hi, > > I would like to (finally) prepare a first release of the Apache > Commons OGNL project. I'm reading the docs [1][2], which I think is > enough to prepare the release. > > Is it possible to release a version just to learn how to do the > release? I mean, there is still a lot of code that I would like to > fork from the original source [3], but this is a manual process and in > the meantime I would like to test/learn the release process. > > [1] https://commons.apache.org/releases/prepare.html > [2] https://commons.apache.org/proper/commons-release-plugin/index.html > [3] https://github.com/jkuhnert/ognl > > > Regards > -- > Łukasz > + 48 606 323 122 http://www.lenart.org.pl/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > >
