Versioning, deployment improvements

I’ll preface by saying that the current setup (deploy every push to master) works well for me and I prefer it over manually creating tags/releases.

I do however have two wishes:

• limit to one release per day
• shorter version numbers (17.7.8 instead of 17.7.8.1317)

Travis recently added a daily cronjob feature which we could use to implement daily deployment, but it runs regardless of changes.

These changes are possible but we need two pieces:

• something that stops Travis as soon as it sees no new commits since the last build (which might not be exactly 24 hours before)
• something that stores the previous version in Travis’ cache (seems possible) as y.m.d and automatically bumps it to y.m.d.1 if multiple builds happen in the same day

Ideas? Have you seen such packages? Know how to do this?

[sindresorhus]

I would prefer to use a hosted service unless we really can’t. I hate doing DevOps and we have better things to spend our time on than manage a Jenkins instance.

[sindresorhus]

@bfred-it I think we should just go with the daily cronjob right now and we can figure out how to only release when there are new commits later on.