> [X] General Availability (GA)
+1 (binding)
Thank you
Johannes
#
web: https://www.jgeppert.com
twitter: https://twitter.com/jogep
Am Fr., 1. Sept. 2023 um 08:44 Uhr schrieb Lukasz Lenart <
lukaszlen...@apache.org>:
> The Apache Struts 6.3.0
[X] General Availability (GA)
Markus
Am 01.09.23 um 08:44 schrieb Lukasz Lenart:
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
pt., 1 wrz 2023 o 08:44 Lukasz Lenart napisał(a):
> [X] General Availability (GA)
+1 (binding)
Regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
-
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
For
[X] General Availability (GA)
On Fri, 1 Sept 2023 at 16:44, Lukasz Lenart wrote:
>
> 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 /
Works great for me. Thanks.
[x] General Availability (GA)
On 01/09/2023 07:44, Lukasz Lenart wrote:
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
As no objections have been made, I'm going to drop the current build &
tag, merge Kusal's fix and re-release 6.3.0 again :)
czw., 31 sie 2023 o 12:36 Lukasz Lenart napisał(a):
>
> czw., 31 sie 2023 o 09:44 Greg Huber napisał(a):
> >
> > Is this vote still open?
>
> This is an open question, we
czw., 31 sie 2023 o 09:44 Greg Huber napisał(a):
>
> Is this vote still open?
This is an open question, we can continue with the current build and
once accepted quickly release a new version 6.3.1 which will include
the fix from Kusal.
Regards
--
Łukasz
+ 48 606 323 122
Is this vote still open?
On 30/08/2023 12:01, Lukasz Lenart wrote:
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
No preference here
KUSAL KITHUL-GODAGE
Software Engineer
On Wed, 30 Aug 2023 at 21:01, Lukasz Lenart wrote:
>
> 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
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
10 matches
Mail list logo