- 🇺🇸United States smustgrave
@TR I've just been added as co-maintainer. I've been working on getting some fixes into 8.x-1.x as that is stable but eventually want to turn attention to 2.0.x branch. Would you be willing to open tickets based on what you've already seen that needs to be done.
- 🇺🇸United States smustgrave
Is it documented anywhere the direction/goals of 2.0.x?
- 🇺🇸United States tr Cascadia
Is it documented anywhere the direction/goals of 2.0.x?
No. 2.0.x was developed in private without any issues in the queue to track what was done and without any input from the community. And as I said, a lot of fixes that were put into 8.x-1.x didn't get forward ported into 2.0.x, so a lot of work is going to have to be repeated to fix this up.
Would you be willing to open tickets based on what you've already seen that needs to be done.
OK, but it's a huge amount of work. The 2.0.x branch is a mess. I'll start with the simple things.
- 🇺🇸United States smustgrave
Appreciate it! In the meantime we will keep the 8.x-1.x going and fully supported with new changes, fixes, etc. Until a time we can switch to 2.0.x.
Biggest issue I've seen so far is there's no backwards compatibility. Any usages of the old service used will break on 2.0.x.
- Status changed to Closed: outdated
almost 2 years ago 1:59am 29 January 2023 - 🇺🇸United States smustgrave
Closing this one out as there are no active tasks to be had
8.x-1.x will continue to be supported until the time 2.0.x is useable.
We will somehow implement a BC layer between 8.x-1.x and 2.0x
All work for 8.x-1.x will also be tested on 2.0.x to make sure all changes stay captured and no work is lost.