There is a blocker [1] discovered by Kusal, should I merge the PR into the master branch and roll a new release -> 6.3.1 or rather clean up everything and start over with 6.3.0. Some uses get confused if there is there is a patch release without having a minor release (having 6.3.1 without releasing 6.3.0)
[1] https://github.com/apache/struts/pull/744 Regards Łukasz śr., 30 sie 2023 o 10:50 Lukasz Lenart <lukaszlen...@apache.org> napisał(a): > > The Apache Struts 6.3.0 test build is available. With this release the > following issues were addressed: > > Improvement > [WW-5233] - Include Apache Tiles code base in the Tiles plugin > [WW-5321] - notify / document about new maxStringLength limitation > [WW-5327] - Stop using JavaBeans notation for setters in > SecurityMemberAccess & MemberAccessValueStack > [WW-5332] - Validate excluded package name list for missing commas > [WW-5334] - Misc VelocityManager code cleanup > [WW-5336] - Merge OgnlTool class into StrutsUtil class > [WW-5337] - Improve performance of excluded classes and packages > > Bug > [WW-5330] - Issue when submitting a form with a textarea containing > more than 4000 characters. > [WW-5331] - Access to request attributes via tags is broken > > Dependency > [WW-5315] - Upgrades ASM to version 9.5 > [WW-5316] - Upgrades commons-io to version 2.13.0 > [WW-5317] - Upgrades log4j-api to version 2.20.0 > [WW-5318] - Upgrades slf4j-api to version 2.0.7 > [WW-5320] - finish Reproducible Builds > [WW-5322] - Upgrade Jackson version to 2.15.2 > [WW-5323] - Upgrade JasperReports to version 6.20.5 > [WW-5325] - Upgrade commons-lang3 to version 2.13.0 > [WW-5329] - Upgrade xstream to version 1.4.20 > > Release notes: > * https://cwiki.apache.org/confluence/display/WW/Version+Notes+6.3.0 > > Github release > * https://github.com/apache/struts/releases/tag/STRUTS_6_3_0 > > Distribution: > * https://dist.apache.org/repos/dist/dev/struts/6.3.0/ > > Maven 2 staging repository: > * https://repository.apache.org/content/repositories/staging/ > > Once you have had a chance to review the test build, please respond > with a vote on its quality: > > [ ] Leave at test build > [ ] Alpha > [ ] Beta > [ ] General Availability (GA) > > Everyone who has tested the build is invited to vote. Votes by PMC > members are considered binding. A vote passes if there are at least > three binding +1s and more +1s than -1s. > > The vote will remain open for at least 72 hours, longer upon request. > A vote can be amended at any time to upgrade or downgrade the quality > of the release based on future experience. If an initial vote > designates the build as "Beta", the release will be submitted for > mirroring and announced to the user list. Once released as a public > beta, subsequent quality votes on a build may be held on the user > list. > > As always, the act of voting carries certain obligations. A binding > vote not only states an opinion, but means that the voter is agreeing > to help do the work. > > > Kind regards > -- > Łukasz > + 48 606 323 122 http://www.lenart.org.pl/ --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
