No, please not, as long as https://bugs.maemo.org/show_bug.cgi?id=6187 isn't resolved. I refuse to use the XB-Maemo-Upgrade field as long as this bug exists.

If I knew that Upgrade field breaks the Downloads description then I wouldn't have used it...

I don't think that upgrade field is used in downloads or packages interface atm

There's also a vague plan, AIUI, to have maemo.org/packages/ show the changelog. Another problem with XB-Maemo-Upgrade-Description is that you don't know what version a user is upgrading from; so they see "Small UI tweak" but they skipped over "Major rewrite with loss of functionality".

I would strongly plead for this vague plan to be be implemented. Whenever I searched for a changelog in the packages, except for one instance, I didn't find it. If the changelog figures on the packages page, package maintainers would have a motivation for this minimal piece of documentation. Even if the information is minimal, it would make me much more comfortable in installing things from maemo.org.

(Even better would be a bit more documentation and not have everything served as Easter eggs but that's perhaps too much to ask for)

Find a developer who knows PHP, is willing to work on the source code, and will talk to X-Fade & Jeremiah about the implementation. That's the quickest way to get it done: scratch an itch.

https://garage.maemo.org/plugins/scm...=maemo2midgard

I dunno when X-Fade will get around to it, with everything else on his plate (one to ask at the next sprint meeting/on maemo-community).

Call be arrogant or ignorant, but the internal changelogs are way too heavy to be of any particular use: For instance the internal Debian changelog of libosso-abook right now weights 103 kByte and 1969 lines. The internal changelogs of many other packages are of similar weight or even heavier. They become that large because they are deeply integrated with the QM process. Shipping them would give everyone a really nice feeling, but I am pretty sure only very few people would actually read them. You'd get bored about them quickly with all the QM noise. Waste of disk space and bandwidth. IMHO.

I sometimes read changelogs. Having them always present is just good practice and means that when I want to know what has changed my curiosity is satisfied - not having them available means I'm left frustrated and annoyed/concerned by the broken process, as changelogs are the norm on other related platforms (Debian, Ubuntu etc.).

I too would also tend to steer clear of applications where the developer(s) are too lazy and/or too unprofessional to maintain a list of the changes - a changelog is not an indication of quality, but it does at least suggest a minimum level of competence.

Obviously a number of changes are necessary to promote the use of changelogs in both the App Manager on the device and the maemo.org website itself, but there should be no question that they are useful and should be made available, I would even go so far as suggesting that applications should not be promoted to extras unless each update is accompanied by a current changelog.

I don't think the additional disk space consumed by changelogs should be an issue - text compresses very well.

Hmm... any update on this?
http://maemo.org/packages shows now mostly a proper changelog. Are there plans or active development, to integrate something like this into the on the device integrated package manager?

In my opinion this is in the most cases as important as the package description.

Maybe you can ask that in the Faster Application Manager thread!?