[Question] Versioning of re-implementation - 1.0.0 or 2.0.0? #448

Open
opened 2026-02-17 12:06:20 -06:00 by GiteaMirror · 4 comments
Owner

Originally created by @tschaka1904 on GitHub (Dec 14, 2020).

Assuming that we have a project called: "WizardProject".

The WizardProject, which currently stands at version 1.x.x, has a mostly Java based stack and active development has been discontinued on it.

Now, we want to bring the WizardProject back to life. Everything is new, but the same idea behind it, as well as the same name. A new repo gets created and the stack changes dramatically form Java to Python.

The new implementation of the WizardProject doesn't carry any code from the prior implementation, but obviously it is heavily inspired by version 1.x.x.

Would the implementation of the WizardProject be 2.0.0, as it is based on an existing idea? Or should it be version 1.0.0, as it is basically an all new implementation?

Originally created by @tschaka1904 on GitHub (Dec 14, 2020). Assuming that we have a project called: "WizardProject". The WizardProject, which currently stands at version 1.x.x, has a mostly Java based stack and active development has been discontinued on it. Now, we want to bring the WizardProject back to life. Everything is new, but the same idea behind it, as well as the same name. A new repo gets created and the stack changes dramatically form Java to Python. The new implementation of the WizardProject doesn't carry any code from the prior implementation, but obviously it is heavily inspired by version 1.x.x. Would the implementation of the WizardProject be 2.0.0, as it is based on an existing idea? Or should it be version 1.0.0, as it is basically an all new implementation?
GiteaMirror added the question label 2026-02-17 12:06:20 -06:00
Author
Owner

@ljharb commented on GitHub (Dec 14, 2020):

Does a user using v1 have to have any different platform requirements than one of v2? Specifically, java or python installed, or not installed?

If the platform requirements have changed, it's semver-major.

If you want to reset to v1.0.0, the project would need a new name, which might also be a good idea.

@ljharb commented on GitHub (Dec 14, 2020): Does a user using v1 have to have *any* different platform requirements than one of v2? Specifically, java or python installed, or not installed? If the platform requirements have changed, it's semver-major. If you want to reset to v1.0.0, the project would need a new name, which might also be a good idea.
Author
Owner

@alexandrtovmach commented on GitHub (Jun 14, 2021):

@tschaka1904 is it helpful?

@alexandrtovmach commented on GitHub (Jun 14, 2021): @tschaka1904 is it helpful?
Author
Owner

@jwdonahue commented on GitHub (Nov 29, 2021):

I agree with @ljharb, you should probably rebrand the product and side-step the version issue entirely. Otherwise, it's requires a major version bump. Your java customers probably can't upgrade to the new implementation, so it's breaking for them.

@jwdonahue commented on GitHub (Nov 29, 2021): I agree with @ljharb, you should probably rebrand the product and side-step the version issue entirely. Otherwise, it's requires a major version bump. Your java customers probably can't upgrade to the new implementation, so it's breaking for them.
Author
Owner

@jwdonahue commented on GitHub (Nov 29, 2021):

And somebody should close this old thread.

@jwdonahue commented on GitHub (Nov 29, 2021): And somebody should close this old thread.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/semver#448