| Summary: | My kate version is not listed in the possible versions. | ||
|---|---|---|---|
| Product: | [Applications] kate | Reporter: | Salvo "LtWorf" Tomaselli <tiposchi> |
| Component: | part | Assignee: | KWrite Developers <kwrite-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | christoph, mail, subscriber |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Debian unstable | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Salvo "LtWorf" Tomaselli
2015-10-01 12:30:15 UTC
I just noticed the same thing. This seems to be very much a WTF kind of thing and was reported 6 months ago. Is it too much to expect someone to reply to this? Yes, we should add these versions ... but it's quite a lot of versions, that will be a problem again I guess. Forgive me if I'm reading too much into that reply....but is there an implied "...therefore we don't / won't do it?" Isn't updating the bug tracking system with the new version simply a standard part of the release process? Isn't it among the most basic things developers should do to maintain the most basic level of professionalism? Or is this bug system deprecated and some other one meant to be used for Kate? Or is Kate essentially an unmaintained project? I'm really struggling to make sense of this... There's an implied "I won't do it right now because I have other things to do but I agree that somebody should do it, though I see it coming that this problem will be there again in six months unless it gets automated". There is no need to question the whole world because of such a minor issue ... just select unspecified and all will be good. If you can't update it, remove the field and hope people add it in their bugs. Versions added. |