Skip to content
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

Move to semver #24

Closed
caoimhebyrne opened this issue Apr 24, 2023 · 1 comment
Closed

Move to semver #24

caoimhebyrne opened this issue Apr 24, 2023 · 1 comment
Labels
enhancement New feature or request

Comments

@caoimhebyrne
Copy link
Owner

Our current way of deploying is pushing to dev and then getting people to update their commit hashes, which is not ideal.

Instead, we should have a development branch, and a main branch. We push to development during a work-cycle, and once it is ready for release, we push to main with a bumped version.

Right now, I would consider the project to be in 0.1.x, but since we haven't used semver since the start, I'm unsure of what the exact version would be.
@caoimhebyrne caoimhebyrne added the enhancement New feature or request label Apr 24, 2023
caoimhebyrne added a commit that referenced this issue Apr 24, 2023
@caoimhebyrne
Meta: Set version to 0.2.0
835a363 
We weren't following any versioning... until now!
This is related to #24
@caoimhebyrne
Copy link
Owner Author

Ok, we now have a main and development branch. This issue is probably okay to be closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@caoimhebyrne