[build] official release package in deb and rpm format

[LeoHChen]

Summary

We are using a customized release package so far.
We have to build many customized deployment script and configuration scripts around it for validators.

To facilitate the installation and upgrade process, we need to build the format of the standard package using Deb or RPM packages.
Standard packages have many advantages like detailed documentation, many supporting tooling, easy integration, and lower learning curve.

TODO

• build rpm package
• build deb package
• sign package using official pgp signature
• automate the version/changelog of the package
• release package in public repo for rpm/deb
• testing plan document
• publish and update repo process need more test and automation
• test by p-ops
• test by validators
• autonode support
• updated ansible script, work with Blockdaemon: https://github.com/Blockdaemon/harmony-deploy
• update jenkins release job to build/sign/publish rpm/deb package
• official document for the standard package installation/upgrade
• release to public

[LeoHChen]

https://gist.github.com/LeoHChen/cada1c9a30c1406c80dc9c84e1fd99b6

[mindstyle85]

what happens if youre already on systemd and on a non root user, but youre using a different user than this package suggests (harmony)? will it override everything or will it check if any existing users are there/and possible systemd files?

[LeoHChen]

I'd suggest setting up a new host for the new package.

[LeoHChen]

RPM and DEB packages are built during release process.