Plasma versions in bugs.kde.org

[Alexander Potashev]

Thanks Jonathan!

For https://bugs.kde.org/enter_bug.cgi?product=ksysguard it's currently
possible to pick from a longer list of versions, e.g. 4.12.0, 5.0.0. Is
this intended?


Regarding reporting bugs in unsupported versions via bugs.kde.org, it might
be frustrating not a find a version that one is using, and see no
explanation for the limited list in the versions drop-down. OTOH as I
understand it's not really possible to communicate to the user in Bugzilla
UI :(


On Fri, Sep 10, 2021, 15:54 Jonathan Riddell <jr at jriddell.org> wrote:

> You can't change to an old inactive version number no, bug reports
> shouldn't be made without testing the latest version in general.  It's easy
> to do this with e.g. neondocker images.
>
> Jonathan
>
>
> On Fri, 10 Sept 2021 at 14:10, Nate Graham <pointedstick at zoho.com> wrote:
>
>> On 9/10/21 2:17 AM, Alexander Potashev wrote:
>> > Hi,
>> >
>> > If someone wants to report a bug against an older version, what would
>> > you suggest and/or expect them to do?
>> >
>> > I can imagine I would still report bugs while setting version number to
>> > "unspecified" and then mentioning the version in the bug report text.
>> >
>> > Will it be possible to change version number to an older version after
>> > the report has been created?
>>
>> You can always do that when using bugs.kde.org directly. The discussion
>> in question only really concerns filing automatic crash reports from
>> DrKonqi, as it will now prevent you from doing so if you're using an
>> unsupported version. Instead it will display a message saying something
>> along the lines of, "Sorry, this version is too old; consider upgrading."
>>
>>
>> Nate
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/plasma-devel/attachments/20210910/8f803fbd/attachment.htm>