automate release process

[salomvary]

create a Makefile to

• bump version
• build & sign .dmg
• update appcast
• update website

[vitorgalvao]

Two related notes:

• There’s no release on github for 0.18.0 (it’s on the README, but not on the releases page).
• There’s already an automated appcast, one that github makes, here (simply add .atom to the releases page URL).

[salomvary]

Thanks, fixed, forgot to push the 0.18 tag.

The automated appcast isn't quite the same as the "manual" one. Compare:
https://github.com/salomvary/soundcleod/blob/master/appcast.xml
https://github.com/salomvary/soundcleod/releases.atom

appcast.xml is used for automatic updates and has to conform this specific schema (afaik).

[vitorgalvao]

Yes, they’re not the same, but they can be made pretty similar. You control the software, so if you release it (and actually append an app to download, instead of simply releasing the source) through github’s release page in a consistent manner, you can just as well grab that file and do what needs to be done to get the new version.

In the end, and appcast is just a text file, and you control its contents. It’s structure is, therefore, irrelevant because you can make your script just care about what you want consistently.

[salomvary]

Yep, however I did not implement automatic updates myself. SoundCleod uses Sparkle to do the heavy lifting. For good reasons there is no easy way to replace appcast with the github releases atom feed.

See also sparkle-project/Sparkle#648

[salomvary]

As the Makefile does most of the releasing automatically, closing this.