New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Tag and version DCF releases #293

Open

skoolbus39 opened this issue Oct 7, 2019 · 1 comment

Member

skoolbus39 commented Oct 7, 2019

No description provided.

Contributor

macburgee1 commented Oct 8, 2019

Adding formal versioning and tagging will big plus for managing releases moving forward.

I propose we use semantic versioning, which is what NPM uses: https://docs.npmjs.com/about-semantic-versioning.

In terms of a branching strategy, here are some thoughts given the upcoming release of DCF 2.0:

Disuse the "master" branch
Use separate branches for DCF 1.x.x and DCF 2.x.x
Upon release of DCF 2.0.0, only bug fixes and maintenances commits will be permitted for 1.x.x. All new development will happen in 2.x.x.
EOL needs determined for 1.x.x

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment