Clarify 0.x.x versioning #455

Open
opened 2023-06-20 10:28:35 +00:00 by iexos · 2 comments
Member

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
Owner

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.

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.
Owner

@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
Sign in to join this conversation.
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: coop-cloud/organising#455
No description provided.