Fully automate releases

[jariz]

We have the release.sh script now, which helps a lot, but I'd like to extend it further to fully automate a release.
It will need to be extended to do the following:

• Added to the github releases (with the help of release)
• Added to the appcast file on the jariz/Noti-appcast repo
• Run cask-repair noti in order to push it to homebrew

(in that order)

[ABeltramo]

What about Apple codesign? Can we release a public certificate to sign the newly generated app?

[jariz]

xcodebuild (which is ran by release.sh) already applies code signing when using the release scheme

[jariz]

Just read your updated comment.
I'm signing it with a apple developer ID from my company, which requires a private key, so no, I'm the only one that can do releases, I'm afraid.
However, it'd be wise if I (we?) would look into getting our own developer ID.
Problem is that once you start using a developer ID, there's no way to switch as far as I know, because that's kind of the point of the codesigning process, the identity can't change.

But eitherway, if not for this project, possibly future projects.

[ABeltramo]

Don't know why but for "fully automate" I figure something like Travis automatically build the release.