Clarify 0.x.x versioning #455
Labels
No Label
abra
abra-gandi
awaiting-feedback
backups
bug
build
ci/cd
community organising
contributing
coopcloud.tech
democracy
design
documentation
duplicate
enhancement
finance
funding
good first issue
help wanted
installer
kadabra
performance
proposal
question
recipes.coopcloud.tech
security
test
wontfix
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: toolshed/organising#455
Loading…
Reference in New Issue
Block a user
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?
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 recipeYeh 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.
@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.