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.

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

Bump version to 1.6.0 #119

Merged
merged 3 commits into from
Nov 27, 2023
Merged

Bump version to 1.6.0 #119

merged 3 commits into from
Nov 27, 2023

Conversation

hartwork
Copy link
Collaborator

With the slight differences in behavior and the number of improvements maybe "2.0.0" will be a better fit that "1.5.3", so I went for that. Just an idea, and also demos a pull request where UI tests are affected.

@hartwork hartwork changed the base branch from master to development November 26, 2023 16:19
Copy link
Collaborator

@edgar-bonet edgar-bonet left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It makes sense to bump to at least 1.6. Maybe to 2.0 if introducing a behavior incompatible with previous versions, e.g. more tolerant parsing. In the end, I think the decision belongs to @tenox7.

@tenox7
Copy link
Owner

tenox7 commented Nov 27, 2023

I would prefer 1.6 rather than 2.0. I think I want to reserve 2.0 if we completely rewrite it in Go or Rust or something like that.

snap/snapcraft.yaml Outdated Show resolved Hide resolved
@hartwork
Copy link
Collaborator Author

I would prefer 1.6 rather than 2.0. I think I want to reserve 2.0 if we completely rewrite it in Go or Rust or something like that.

@tenox7 alright, re-targeted to 1.6.0 now.

@hartwork hartwork changed the title Bump version to 2.0.0 Bump version to 1.6.0 Nov 27, 2023
@hartwork hartwork merged commit 1cfafdc into tenox7:development Nov 27, 2023
5 checks passed
@hartwork hartwork deleted the bump-version branch November 27, 2023 22:15
@hartwork hartwork added this to the 1.6.0 milestone Nov 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants