toolshed/organising
toolshed/organising
7
1
Fork 0
Code Issues 121 Pull Requests Releases Activity

Clarify 0.x.x versioning #455

New Issue
Open
opened 2023-06-20 10:28:35 +00:00 by iexos · 2 comments
iexos commented 2023-06-20 10:28:35 +00:00
Copy Link

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
Owner
Copy Link

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.
3wordchant commented 2023-06-23 11:45:58 +00:00
Owner
Copy Link

@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 Documentation project 2025-04-20 06:04:31 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
abra
Everything to do with abra
abra-gandi
Abra Gandi plugin
awaiting-feedback
Ping/pong on comms
backups
bug
Something is not working
build
Go build related issues
ci/cd
Getting the robots into the mix
community organising
Opening this thing up
contributing
Contributors stuff
coopcloud.tech
Our main website
democracy
Democratic decision making
design
Design thinking required
documentation
Let's write things together
duplicate
This issue or pull request already exists
enhancement
New feature
finance
Money things
funding
Anything related to grant funding
good first issue
Easy start with development
help wanted
Need some help
installer
Installation related issues
kadabra
performance
Performance related
proposal
Large change which requires feedback & decisin making
question
More information is needed
recipes.coopcloud.tech
Our recipes catalogue
security
Securing our shit
test
Unit or integration test suite
wontfix
This won't be fixed
No Label
documentation
Milestone
No items
No Milestone
Projects
Clear projects
No project Documentation
Assignees
Clear assignees
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: toolshed/organising#455
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?