Aegisub 3.4.0 is out. What's next? What fork should I use now?

[arch1t3cht]

As you might have seen, Aegisub 3.4.0 was released yesterday: https://aegisub.org/blog/aegisub-3.4.0-released/
I expect a lot of people to be wondering what version they should be using now, so let me clear that up here.

First of all, as you might have seen from the release post, I was involved in the 3.4.0 release and have push access to the TypesettingTools/Aegisub repository (which is now effectively the official Aegisub repository). The long-term plan is for development to move over to TypesettingTools/Aegisub, and to merge in the additions from my fork.

For the 3.4.0 release, the goal was to just get a new stable release out that uses the new meson build system. Most of the bugfixes from my fork were merged into that release, but almost none of the new features - that would have blown up the scope too much. Hence, apart from internal modernization refactoring and a few very small fixes, all the additions from 3.4.0 are also in my fork (i.e. my Release 12). Thus, if you already have my version installed, probably do not want to update to 3.4.0.

That said, any people testing 3.4.0 and pointing out anything that breaks (i.e. anything that used to work on 3.2.2 but doesn't any more) would be very appreciated. If you do not need any of the new features in my fork or are migrating from 3.2.2 or r8942, testing 3.4.0 would help development a lot.

As for what's next, the plan is of course to eventually merge most of the additions from my fork into TypesettingTools/Aegisub (i.e. the now official version). However, this will need to be done very carefully. Apart from needing to rebase everything on top of the large list of internal refactors added in TypesettingTools/Aegisub, there are some additions on my fork that I regret or would want to do differently. Some changes (e.g. the new video providers or the perspective tool) should be fairly uncontroversial and be upstreamable fairly quickly, some (e.g. the audio player rework and line folding) are ones I'd at least want to revisit, and some (e.g. the "align to video" feature from wangqr/Aegisub, which should ideally be turned into an automation script of some kind) are ones I am thinking about not even upstreaming at all.

So, expect this migration to take some time. I'll try my best to keep arch1t3cht/Aegisub updated with any big user-facing changes added exclusively to TypesettingTools/Aegisub, so that there will be a clear moment in time when everyone should switch over to TypesettingTools/Aegisub.

Finally, I need to mention that this is still a hobby project and that, just like everyone else, I have a job and a life and other hobbies. I am very grateful for any and all bug reports and pull requests, but I cannot promise to always get to them quickly. Especially since, now that I am working on upstream, I need to be even more careful with any changes I make. Please don't take a lack of a response as a lack of interest, it may just be a lack of time.

[itschasa]

aegi updated after a decade, this is not a drill 🚨🚨🚨

[skysphr]

So in other words your fork remains the de facto bleeding edge, correct?