Support RC releases for recipes #241
Open
opened 2021-11-09 09:36:15 +00:00 by decentral1se
·
5 comments
Labels
Clear labels
abra
awaiting-feedback
backups
bug
build
ci/cd
community organising
contributing
coopcloud.tech
design
documentation
duplicate
enhancement
fedi
fedi-infra
finance
funding
good first issue
help wanted
installer
legal
performance
proposal
question
security
test
wontfix
Everything to do with abra
Ping/pong on comms
Something is not working
Go build related issues
Getting the robots into the mix
Opening this thing up
Contributors stuff
Our main website
Design thinking required
Let's write things together
This issue or pull request already exists
New feature
Democratic decision making
Money things
Anything related to grant funding
Easy start with development
Need some help
Installation related issues
Performance related
Large change which requires feedback & decisin making
More information is needed
Securing our shit
Unit or integration test suite
This won't be fixed
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
3wordchant
aadil (Aadil Ayub)
abra-bot (Abra Bot)
ammaratef45
amras (Sarma)
Apfelwurm
BornDeleuze
Brooke
carla
cas (Cassowary)
coopcloud
cyrnel
decentral1se (d1)
dede
devydave
fauno (fauno)
iexos
jade (Jade Ambrose)
jjsfunhouse
jmakdah2 (Jackie Makdah)
joe-irving (Joe Irving)
kawaiipunk (KawaiiPunk)
knoflook
kolaente
lambdabundesverband
linnealovespie (April)
moosemower
moritz
notplants
oxaliq (sorrel)
p4u1
pharaohgraphy (Andrew 🐦🔥❤️🔥✴️)
renovate-bot (Comrade Renovate Bot)
ripclap
simon
sixsmith (Sixsmith)
stevensting
trav (Trav Fryer)
val (val (he/him))
yksflip
Clear assignees
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: toolshed/organising#241
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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