+1 to NOT maintain 9.x, most people will not use it anyway Richard Zowalla <r...@apache.org> schrieb am Di., 7. Feb. 2023, 19:59:
> Hi all, > > I wanted to bring this thing to the list, which appeared in a slack > chat today. > > Back in October 2021 we had a discussion on how we want to handle our > three active branches (8.x, 9.x and main/10.x) in terms of maintainance > [1]. We already agreed in another thread, that we are not activley > maintain 7.0.x or 7.1.x (but are open for contributions) anymore. > > Now, we have a 9.0.0 released, which passes the TCK (which by itself is > really a great achievement!) and we are dived into the EE10 work to > have the momentum. > > However, we missed to find consensus on the different proposals and > arguments and didn't make a decision or a vote back than. Currently, I > am seeing, that we are doing work on three different branches and > porting things back and forth ;-) - the situation is a bit agile (lol) > and it is really difficult to keep track (even if it only affects > common dependency updates). > > At the moment, we have: > > - 8.x (EE8) > - 9.x (EE9) > - 10.x/main (EE10) > > Keeping up with three diverging code bases is challenging ;-) > > In addition, the situation is complicated by the fact, that the Tomcat > project decided to EOL their 10.0.x line, which is targeting EE9 and > won't get any fixes in the future. > > I think, that we should discuss our prorities in maintaining the > different branches, ie. how much "love" (or energy) we want to give > each branch (if someone steps up and keeps up porting changes, I > wouldn't be against it). > > Personally, I think, that we should keep up our efforts in maintaining > 8.x (as it is the last javax version and industry will need some more > adoption time before moving to jakarta), ie fixing build improvements, > bug & cves but put the vast majority of our energy into the EE10 work > (+ related projects). I don't think, that we have the energy to > backporting a lot of things to the 9.x branch (aside from CVE fixes, > which might be difficult to the eoling of some libs)) though - but > again: If someone steps up and has the energy to do that, I won't > object :-) > > Any thoughts or ideas on a strategy? > > Gruß > Richard > > > > > > > [1] https://lists.apache.org/thread/z953f2th5kqc3brjvcjmjwwo93hcd970 > >
