Make diff of built files between releases visible

[lejoe]

We want to improve the communication with people integration the code we deliver.
For now we can only communicate the changes in the source files.
It's harder to do this for the built files.
We want to improve this.

[lejoe]

Idea:

We have a release branch.
Let's have also a release-build branch.

The release contains the source files
The release-build contains only the built files.

We should automate this because manual syncing is a bad idea.

[lejoe]

Proposed solution

New step on snap-ci called "release"
It's a manual step.
When clicking on it, it calls a gulp task that:

• bump the version in the package.json file *
• merges master to release
• commits the built files to release-commit
• creates a release tag *
• uploads a zip to the release *

* not compulsory in first version

Related to #58

[lucalanca]

can we checkin the build/ folder on the release branch?

[lejoe]

I want to avoid that because it creates noise in the diffs.
We never had a partner that used our source files so I don't think they are interessted in both diffs at the same time.

[peterbraden]

Do we really need the release zips? Unless a client really wants them, I think the tag is fine. Especially if we have a branch with build checked in.

[lejoe]

Right. will do without for now.

[lejoe]

Updated:

bump the version in the package.json file *
merges master to release
commits the built files to release-built
creates a release tag *