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

A very kind suggestion to adjust Empirica versioning #531

Open
2 tasks done
kaglowka opened this issue Mar 29, 2024 · 2 comments
Open
2 tasks done

A very kind suggestion to adjust Empirica versioning #531

kaglowka opened this issue Mar 29, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@kaglowka
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

What happened?

Hi! I'm just getting familiar with Empirica (and thank you for this incredibly helpful framework!), so I'm perhaps in no position to demand changes, but I found the current version mismatch confusing (1.x.x releases corresponding to what's called Empirica 2 in the documentation).

I understand it's not an easy thing to adjust it now (and could cause further confusion), but I thought I'd create an issue to:

  • track this version mismatch, so it's easy to signal if others find it problematic, too.
  • be able to take the next good opportunity to adjust the versioning.

Steps To Reproduce

Actually I was trying to run a game based on Empirica 1, and at first I couldn't understand where the transition between Empirica 1 and 2 happened if this repo contains mostly 1.x.x releases.
The comment at release 1.0 clarified it for me: https://github.com/empiricaly/empirica/releases/tag/v1.0.0

Empirica Version

No response

What OS are you seeing the problem on?

No response

What browser are you seeing the problem on?

No response

Relevant log output

No response

Anything else?

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
@kaglowka kaglowka added the bug Something isn't working label Mar 29, 2024
@npaton
Copy link
Contributor

npaton commented Mar 31, 2024

Thank you for your feedback. I agree it's confusing. I'm afraid a version change now would be equally as confusing. It would signal to some that a major and backward-incompatible change happened, while it didn't. I'm torn. I obviously should have skipped to 2.0.0 on the first release. Now, I don't know. If people have opinions either way, please share them here.

@kaglowka
Copy link
Author

kaglowka commented Apr 8, 2024

Sure, I fully agree there's no clean solution now.

The best idea I can think of now is to take the opportunity if any backwards-incompatible changes are in fact made and make a jump to version 3.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants