maemo.org Bugzilla – Bug 3432
Comments on downloads.maemo.org should automatically contain version number
Last modified: 2014-03-08 10:19:57 UTC
You need to
before you can comment on or make changes to this bug.
STEPS TO REPRODUCE THE PROBLEM:
1) Go to: http://maemo.org/downloads/product/PC/tablet-encode/
2) View comment by chmac.
Header of the comment would contain a message like "Made against v2.18" or a
footer appended to the message along the lines of: "This comment was made
against an earlier version of this application (v2.18)"
Comment about broken GUI still seems relevant to latest version which has fixed
GUI crashes which could occur in some cases.
Either the meta-data of the comment should contain "against v2.18" - i.e. the
current version when the comment was made. Or, it could not be displayed and -
when a later version is released - the comment appears with a footnote as
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9)
You don't know that the commenter is using an up-to-date version unless they
mention it, so an automatic "Made against v2.18" based on the latest available
version at the time could be misleading. Perhaps something along the lines of
"The following comments were posted before the release of version 2.19:", or,
just make sure the "Changes" section comes with a date. (The "Updated" date up
top is earlier than the comment date which given the context in this bug seems
Even a "this comment was made before the current release" would suffice. This,
combined with #3460, would be sufficient I think.
The "updated" date seems to be another bug - raised as #3485.
I also have my doubts about any automatic reference to dates or versions. If a
user complains about X an the 23 new updates are released, as a reader I still
have no clue whether the complaint was addressed.
Instead having the developer or someone commenting "This is now fixed" in the
very same thread would be much more useful. And human.
If people could get CCed on new comments on the apps they commented, the
original reporter could come back and say "Thank you! Just downloaded the last
version and it rocks!" Verrry nice.
The data model we have in n.n.comments would allow commenting to comments
(threaded discussion), but current UI does not. Should we start working on
(In reply to comment #4)
> The data model we have in n.n.comments would allow commenting to comments
> (threaded discussion), but current UI does not. Should we start working on
I think that would be nice.
I have experimented on internal with adding the version number to the comment,
but that still leaves you with version numbers without a context(of what is
fixed in a release). But on the other hand it is a good indicator for people
who do know?
Maybe adding both would be a good thing here?
> Either the meta-data of the comment should contain "against v2.18" - i.e. the
> current version when the comment was made. Or, it could not be displayed and -
> when a later version is released - the comment appears with a footnote as
> described above.
Maybe there could be a drop down list with all the release numbers for the
package with "unknown" entry as the default and version numbers ordered from
latest to oldest. If commenter doesn't change "unknown" to a real version
number, there would be note like "vX.Y was latest version in <maemo release
name> when this comment was made".