Yeah i understand your case with "only migrate when we implement new features" but i also have to say that currently its winter and i have more time
so better now than never and its unlikely that we ship much releases this year, so i dont think we have any big or even any real overhead maybe only like merging 1 commit and do 1 release :D Romain Manni-Bucau <rmannibu...@gmail.com> schrieb am Di., 10. Jan. 2023, 15:02: > I'll probably be on the same camps than for others, if you plan to impl new > jakarta features a clear +1 otherwise let's wait codebase need changes > cause it reduces costs until it happens (so more a -+0). > > Le mar. 10 janv. 2023 à 13:51, Jean-Louis Monteiro < > jlmonte...@tomitribe.com> > a écrit : > > > Big +1 > > After running into this for months, I don't see benefits in shading > really. > > Creating a maintenance branch for 2.x and moving main/master to 3.x is > the > > way to go in my opinion. > > > > > > If you need, I can help. I upgraded already the BVal TCK in TomEE in this > > PR https://github.com/apache/tomee/pull/1002 > > > > So far I only see 4 failures but I need to update the API to EE 10 and > run > > again. > > -- > > Jean-Louis Monteiro > > http://twitter.com/jlouismonteiro > > http://www.tomitribe.com > > > > > > On Tue, Jan 10, 2023 at 1:47 PM Thomas Andraschko < > > andraschko.tho...@gmail.com> wrote: > > > > > Hi, > > > > > > i would like to finally migrate BVal to the jakarta namespace. > > > WDYT? > > > I would create a 2.0.x branch and set master to 3.0.0-SNAPSHOT. > > > > > > I know that shading has benefits but as we dont have that many releases > > > each year, i dont think its a big problem for us to handle master and a > > > second branch if we really need a release. > > > Also check our JIRA - we dont have any recent bug reports. > > > > > > Best regards, > > > Thomas > > > > > >
