Support RC releases for recipes #241
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?
See coop-cloud/organising#241 (comment)
this will also have to be done for recipes at some point but if i had to guess it's 5-6hrs of work at least so maybe later
Good point! I was just thinking about
abrafor now, since that is where the most breakages are happening.I was hoping some of the CI/CD discussions would bring us to more reliable recipe releases? Maybe we do need a
-rcpraxis there too 🤔 I think the current logic ofabrawould simply publish-rctags in the versions listing for each recipe so maybe we just need to separate that in some UI/UX work?Or what did you have in mind?
yeah that's what i'm thinking too. I think we should have a
--rcswitch forabra recipe releasebut i'm not sure how to implement it. maybe you'd doabra recipe release --minor --rc <app>for the first rc and thenabra recipe release --rc <app>for the following rc's and when you're ready to release the stable versionabra recipe release <app>and it would figure it all out?i.e. starting with croc 1.0.0
abra recipe release --minor --rc croccreates 1.1.0-rc1 tag thenabra recipe release --rc croccreates 1.1.0-rc2, 1.1.0-rc3 etc depending how many times you run itabra recipe release croccreates 1.1.0Sounds good!
--rcgenerating and maintaining the-rc<n>value seems handy to do.coop-cloud/abra#123 got done, changing issue title to reflect focus on recipes now.
Support release candidate releasing/taggingto Support RC releases for recipes