It is perfectly fine to use something like fpcupdeluxe as well.
Personally I prefer to keep everything in my own control. That way there is no need to explain things related to fpcupdeluxe
(e.g. fpcupdeluxe might decide to pick a specific hash for a certain build for example. I simply do not know if something like that is the case for macos and 3.99). What I do know is that fpcupdeluxe uses its own custom build-process and thus might have certain components removed or installed on purpose (it is even customizable in fpcupdeluxe).
In general and with trunk, literally everything is possible: from things that worked in a normal release that are broken in trunk, unable to build trunk et all to features being removed and/or other features having been added. There are no rules for trunk and you use it at your own risk with no guarantees whatsoever.
Having said that, if you do experience regression or other broken behaviour then you are encouraged to report them at the bugtracker so that the developers know these issues exist (and that they can be addressed). In that case you become more or less involved in the development process and requires you to keep an eye on the bug-tracker (so that you do not report something twice and/or support other reported issues either with confirmation (or denial) of the issue, provide additional information or otherwise. Your choice.
I did not experience any issue with trunk from 2 days ago on Linux 64 bit. However do note that issues might only exist on/for a certain platform. As written in one of my previous posts many things have been addressed on/for macos (and they might not all be for the better: your input is valuable if nobody else complained).
Anchordockingdesign was an option on my first startup dialog from Lazarus trunk/main (disquised in the option if you want to use a single window or multiple for the IDE and/or want to have a floating form design window or a docked one).
Recent
