Stationary segments fail to stay merged with adjacent segments after location assignment

Do we have a rough timeline for BIG-174? Is this more like next month or next quarter or next year?

Hi @trackerminerfs! I’ll take this one - it sounds a bit “executive planner” appropriate :wink:

So the numbers and planning answer is: it’s filed for v1.5, medium priority. But that doesn’t cover the nuance of it.

For 1.5 the headliner is going to be GPX import, because there’s quite strong demand for that now. That one’s a biggie, so it won’t be sensible to try to squeeze in another chunky one in the same release. BIG-174 is going to be fiddling about in the guts of core systems, doing foundational architecture stuff.

So beyond 1.5, what are we looking at? That’s where it gets vague. Because the team is literally just me and Claude we have to work in things in serial, one release/feature at a time, and can only realistically plan about one major feature release ahead in time. Each release cycle ends up changing things too much to be able to reliably plan or predict much further ahead than that.

So… I think the best we can do is say that the more people who point at and ask for BIG-174, the more likely it is to arrive sooner (just like GPX import is arriving sooner because there’s been quite a bit of forum noise about it). We log each mention/request in the Linear tickets, and also bump up the priorities based on that demand. BIG-174 is starting to collect more voices now, so it is moving up in that sense!

If I had to put a guess on it… actually I’m still not sure. Will have to feel it out over the next week or two, see how much improvement BIG-408 has had, and how bothersome the remaining failures are. It feels still slightly too early to tell. Although we are seeing mounting feedback here that it is still a problem. So… yeah, playing it by ear.