search

mint-metrics / mojito-js-delivery

🧪 Source-controlled JS split testing framework for building and launching A/B tests.
https://mojito.mx/docs/js-delivery-intro
Other
16 stars 29 forks source link

Releases #57

Closed dapperdrop closed 4 years ago

dapperdrop commented 4 years ago

We should start tagging releases when we do major bug fixes or introduce enhancements to Mojito.

https://help.github.com/en/github/administering-a-repository/managing-releases-in-a-repository

kingo55 commented 4 years ago

Agreed.

For starters we need to decide the versions of releases. We used them internally e.g. the original version of Mojito JS Delivery was 0.5.0 before we stopped doing it. And the Mojito R Analytics version is based on a flat release number - last one was R30.

Also, I think we should also be merging tagged releases into the main Mojito repository for completeness, like how the Snowplow guys handle it, and make the modular approach clearer.

dapperdrop commented 4 years ago

Should we do releases retrospectively as well? It seems like we can tag specific commits, so it might make sense to go back and tag up the major/minor versions against certain commits.

kingo55 commented 4 years ago

Might be useful to get the hang of tagging releases to tag the older commits.

dapperdrop commented 4 years ago

Releases have been retroactively added. Moving forward, we will be regularly tagging release points.

Closing issue.