I’m good with a beta release to come soon. I’m still working on a branch to fix up the remaining SPI updates to avoid guessing at ClassLoaders, but that isn’t required for a beta release. As for the branches, if 2.x was made into 3.0, then main would be 4.0, and where would that leave us? Back in the same debate. I suggest you look at the main branch more closely.
> On Nov 28, 2023, at 4:19 AM, Volkan Yazıcı <vol...@yazi.ci> wrote: > > I plan to work on `main` until February, finalize recycler implementation, > carry out whatever improvement I can, and release `3.0.0`. > > *If you have any objections with this plan, or if you have things to do on > `main` and you cannot comply with this schedule, etc., let's discuss.* I > want to agree on a plan and timeline that works for you. > > *Personal remark:* I am against releasing `3.0.0` from `main`. `2.x` > changes that didn't go into `main` are titanic. `main` also contains > several incomplete code, doc, or both. I support the idea of forking `3.x` > from `2.x`, backporting crucial features from `main` to `3.x`, and then > releasing `3.0.0`. I had several email, Slack, and video conversations with > Ralph, Matt, and Piotr. They don't agree with me. Ralph even threatened to > veto all non-bugfix changes on `2.x` > <https://lists.apache.org/thread/4o9xg0o2csjnf4f372l18f8zjj9c9sy4>. I am > outnumbered and I accept the defeat. Let's release `3.0.0` from `main` and > move on. I don't want to spend time discussing this subject further.
