Clarify 0.x.x versioning #455

New Issue

2023-06-20T10:28:35Z

iexos commented

2023-06-20 10:28:35 +00:00

recipe versioning does not mention usage of pre-1.0.0 versions. Yet e.g. Outline is currently on 0.9.0+...

I'd like to have more clarity on that, e.g. starting with 1.0.0+... as soon as basic functionality is working which means that people might be using the recipe

recipe versioning does not mention usage of pre-1.0.0 versions. Yet e.g. Outline is currently on `0.9.0+...` I'd like to have more clarity on that, e.g. starting with `1.0.0+...` as soon as basic functionality is working which means that people might be using the recipe

decentral1se commented

2023-06-20 13:29:55 +00:00

Yeh good point @iexos! I think we didn't document it and it is basically up to the recipe maintainers at this moment in time? I think a proposal to vote on and stick to would be nice in this regard. Things need to be flexible but having a reference for the possibilities would be good.

3wordchant commented

2023-06-23 11:45:58 +00:00

@iexos the 0.x.y version dates back to our first tangle with Outline, where we were using our own Docker image, including an as-yet-unmerged patch to enable self-hosted SSO.

Now, especially with your excellent contributions, I'm very happy that the recipe is more solid, and enthusiastic for us to launch the version into 1.x.y 🚀

I agree with you and @decentral1se that it'd be nice to have more of a written policy on this kind of situation.

@iexos the `0.x.y` version dates back to our first tangle with Outline, where we were using our own Docker image, including an as-yet-unmerged patch to enable self-hosted SSO. Now, especially with your excellent contributions, I'm very happy that the recipe is more solid, and enthusiastic for us to launch the version into `1.x.y` 🚀 I agree with you and @decentral1se that it'd be nice to have more of a written policy on this kind of situation.

decentral1se added the documentation label 2023-06-29 14:47:13 +00:00

decentral1se added this to the (deleted) project 2025-04-20 06:04:31 +00:00

iexos commented

2026-04-14 10:53:33 +00:00

Maybe we can have another look at this since we now have https://docs.coopcloud.tech/federation/resolutions/passed/025/

How about:

have 0.x.x for recipes which are not yet stable
- following semver, minor bumps are major bumps meaning breaking changes, patch bumps everything else
1+.x.x for stable recipes (and those who where stable at some point)

Maybe we can have another look at this since we now have https://docs.coopcloud.tech/federation/resolutions/passed/025/ How about: - have 0.x.x for recipes which are not yet stable - following semver, minor bumps are major bumps meaning breaking changes, patch bumps everything else - 1+.x.x for stable recipes (and those who where stable at some point)

👍 2

Sign in to join this conversation.

3 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: toolshed/organising#455