TODO before tagging a new release

[bp0]

Packagers need a new tagged release, maybe 5.2 or 5.1.1 or something. See #163, #528, etc... @lpereira, what is the minimum that needs to be done to make it possible?

• [x] Fix GTK3 build (#410, #112)
• [x] Re-instate the server (#532)
• [ ] Fix translation issues when sending stuff to the server (#556)
• [ ] Do not suggest running whole HardInfo as root (#589)
• [ ] Fix licensing issues WRT uber-graph (#702)

[HumanG33k]

it can be nice to have a new release soon. the soft is awesome. There is a milstone feature can help tracking stuff as issue.

[StatusCode404]

Please do a tag ASAP so distros can update their official repo versions!

[lpereira]

This should also be fixed before a release: https://github.com/lpereira/hardinfo/issues/702

(uber-graph is GPLv3, and HardInfo is GPLv2 -- we'll need to either change the license to GPLv2 or later, or use another graphing lib, even if it means porting the GTK2 thing somehow. I'm OK with changing the license to GPLv2 or later, and have made the changes locally, but I have to go through the history of those files to ensure that everyone that touched those files in the past acknowledges/agrees with the change.)

[mckaygerhard]

take into consideration the way how the storage disk are detected does not work with nvme due is not well pointed it! as #687