It seems to me Community was branched off from 10.53.0 and is now 15 commits behind, as of 2024-12-13.
That’s a fair number of Swift6 and core fixes missing already.
I want to keep using Realm locally for a couple of apps for some significant time. I’ve already had one major project cancelled and relationship burned because of the FlexibleSync abandonment.
The deprecation page refers people to the community branches but if they are just going to decay for a year under the Realm github then I think we need a chosen fork and concerted effort to copy across Realm updates.
@Thomas_Goyne sorry for pinging you here but have been seeking an answer for this from the org for some time on github - please let us know about the community branch plans, so that we can take action around a fork now if needed rather than wait a year of decay before getting started on organizing the community around a fork. Thank you!
There’s currently no functional differences between community and master. The Swift 6 changes actually landed on community first, and all of the changes to master after they were split have been CI updates and some sync-specific bug fixes (via a core update).
One litmus test will be if there’s a fix to the current inability to build with Xcode later than 16.0 and deploy on iOS < 15, as discussed here per issue 8708 and 8723
then seeing if that makes it to Community as well as main.