bitpay / bitcore-build

A helper to add tasks to gulp
6 stars 166 forks source link

Drop the releases branch #14

Closed eordano closed 9 years ago

eordano commented 9 years ago

I think there's no actual reason why it needs to be there.

We could have a tag/branch called "current" to signify what's the latest release, but the current schema of "having a branch with merge commits between the last build commit (the ones with the binaries) and the current master be the next release commit" I feel that has no use case or reason to be kept.

yemel commented 9 years ago

Related: https://github.com/bitpay/bitcore/issues/986

maraoz commented 9 years ago

I don't see the need for a special branch for this. That's what tags are for. I vote for removing releases