Why do they not update some features on the Roadmap for weeks?
TL;DRFeatures go stale because they verify the knock-on effects of changes for accuracy first, but they've recognised the gap is too long and plan smaller, more frequent Roadmap updates.
It's due to the complexity, and their desire to have everything as accurate as possible. Publishing the Roadmap is their ability to be transparent about what they're doing, to show their progress and what they plan to do in the future. Their end goal is to give everyone the most up-to-date information, but they also want it to be accurate. So when something on the Roadmap comes in early or late, it has a knock-on effect with something else, so they take the time to verify what impact the change has had, which itself takes time, and then once everything's verified they go through and give an update. What they've realised is that it seems like too much of a gap in between. They've already discussed this internally, and moving forward they're going to change the frequency of the updates, which will mean smaller updates more often. Some of the backend stuff might not be as 100% accurate, because they haven't gone through the entire process yet, but it'll give a clear glimpse of how when they know something moves, they should update the Roadmap to reflect that so that people know what the expectations are. This is also true on the flip side, where if something is finished sooner, then that should be updated as well.