Versioned release, changelog etc. #4
Labels
No Label
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coop-cloud/backup-bot-two#4
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
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?
Thoughts, 3 years later 🫠
App version = changes to
backup.py
.Co-op Cloud package version = changes to recipe.
For example, starting with
1.0.0+2.0.0
(which is what it would be if we released today):1.0.1+2.0.0
backup.py
: increment both, so1.0.1+2.0.1
I (semi arbitrarily?) called the image built from the
bb2-classic
branch1.0.0
, so I suggest we start the new version at 2.0.0.Added a stub
If every new "app" release also increments the Co-op Cloud recipe version (I think it should, as above) then I think "app release" = "packaging release" = bump version in
compose.yml
thenabra recipe release backup-bot-two
.Thoughts @moritz @p4u1 @knoflook @decentral1se ?
I would like to apply the sames rules as discussed in coop-cloud/organising#578 (comment)
This would mean:
1.0.1+2.0.0
1.1.0+2.0.1
Then you can still release in-between recipe patches without updating the image.
👍
👍