Hi question again, since the new faces codebase also is 2.3 compliant, we theoretically could move it into 2.3 next as well, not for this release but in the upcoming future.
Any demand for that? Am Di., 28. Feb. 2023 um 21:07 Uhr schrieb Melloware <[email protected] >: > I think its OK that not everything is backported to 2.3 next we have > been backporting the important things but like Thomas said its not fully > TCK compliant anyway but that is OK. > > > On 2/28/2023 2:55 PM, Volodymyr Siedlecki wrote: > > Hi, > > > > Thanks for the feedback. Expect a vote email in a day or so. > > > > I can make a 2.3-next release after 4.0. However, I know that I didn’t > back-port everything to 2.3-next, so if there's anything of interest, I can > do that first before I start a release. > > > > Best, > > > > Volodymyr > > > > > > On 2023/02/28 19:34:00 Thomas Andraschko wrote: > >> +1 for both releases > >> > >> Melloware <[email protected]> schrieb am Di., 28. Feb. 2023, > 19:26: > >> > >>> I know its a big pain but since we are releasing 4.0 can we release > >>> 2.3-next-m8 as well? > >>> > >>> There are no open issues that I am aware of. > >>> > >>> > >>> On 2/28/2023 1:09 PM, Volodymyr Siedlecki wrote: > >>>> Hello, > >>>> > >>>> I believe we should have everything merged in to pass the TCK (Big > >>>> thanks to Werner!). > >>>> > >>>> However, the TCK is Dependent on these PRs (which I don't see why they > >>>> won't be accepted) > >>>> - https://github.com/jakartaee/faces/pull/1794 > >>>> - https://github.com/jakartaee/faces/pull/1795 > >>>> > >>>> I will verify with one last round of testing with the latest MyFaces & > >>>> TCK updates. If everything comes back green, can we create a final > >>>> 4.0.0 release? I was aiming to create something by Thursday? > >>>> > >>>> Are there any outstanding issues that need to be fixed or merged? > >>>> > >>>> Thanks, > >>>> > >>>> Volodymyr >
