Page 1 of 1

Putting issues on the Roadmap

Posted: 29 Nov 2015, 04:11
by EmperorArthur
I just saw a question on IRC asking about Bug # 2567

It's actually a pretty important playability bug for some people, and it looks pretty easy to fix (using wrong GMST value).

My theory on why this bug and others like it are overlooked because they are not on the roadmap. They don't have a target version.

I propose that we go through the issue tracker and set all issues with target version=none to the latest release. Some will then need to be moved to 1.0 or future, but at least we'll see them on the roadmap.

Re: Putting issues on the Roadmap

Posted: 29 Nov 2015, 09:31
by Zini
Seems we overlooked this one. Happens. But I don't think there is a large scale problem that requires action.
And a clear no to just dumping all issues without a target version into the roadmap. That would be a mess. We would have to review them individually first.

Re: Putting issues on the Roadmap

Posted: 29 Nov 2015, 18:25
by sjek
those 200 which doesn't show up elsewhere than issue search

( ... er_id][]=1 )

one way could be place category marking but without bugtracking it's hard to tell in some cases while some are kinda trivial and already done in that part

and some like this is basically done the setting being in the fallback values ecxept for the "same" part (which would probaply need another system ie. porting to shaders then that time comes)

Re: Putting issues on the Roadmap

Posted: 30 Nov 2015, 12:24
by Zini
The problem with many of these issues is that they are either of poor quality (not enough information to act upon) or redundant. Adding them to the roadmap would just clog things up.