Without actually having looked at the issue track but knowing how such things go down: Less visible progress should be expected right about now even presuming constant development efforts.

The great migration brought many users and uncovered various bugs and requirements for new features and devs have been scrambling to address as much of it as fast as possible -- which means going for low-hanging fruit first and if it's not low-hanging, hack around the issue to produce a quick fix. Now that the worst is over proper software development practice dictates that you should worry more about addressing technical debt you just incurred as well as refactor and redesign until high-hanging fruit are hanging lower so you can pluck them. Doesn't make sense to build 100 ladders when you can take an axe to the tree and fix everything with three very well-planned and executed strikes.