Support RC releases for recipes #241

New Issue

decentral1se · 2021-11-09T09:36:15Z

decentral1se commented

2021-11-09 09:36:15 +00:00

See #241 (comment)

See https://git.coopcloud.tech/coop-cloud/organising/issues/241#issuecomment-10183

decentral1se added the

enhancement

abra

labels 2021-11-09 09:36:15 +00:00

decentral1se added this to the Beta release (software) project 2021-11-09 09:36:15 +00:00

knoflook was assigned by decentral1se

2021-11-09 10:28:06 +00:00

knoflook removed their assignment 2021-11-09 10:28:11 +00:00

knoflook added the due date 2021-11-14

2021-11-09 10:28:15 +00:00

knoflook self-assigned this 2021-11-09 10:29:00 +00:00

knoflook commented

2021-11-09 11:15:38 +00:00

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

decentral1se commented

2021-11-09 11:31:43 +00:00

Good point! I was just thinking about abra for 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 -rc praxis there too 🤔 I think the current logic of abra would simply publish -rc tags 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?

Good point! I was just thinking about `abra` for 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 `-rc` praxis there too 🤔 I think the current logic of `abra` would simply publish `-rc` tags 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?

knoflook commented

2021-11-09 12:00:56 +00:00

I think the current logic of abra would simply publish -rc tags in the versions listing for each recipe

yeah that's what i'm thinking too. I think we should have a --rc switch for abra recipe release but i'm not sure how to implement it. maybe you'd do
abra recipe release --minor --rc <app> for the first rc and then
abra recipe release --rc <app> for the following rc's and when you're ready to release the stable version
abra recipe release <app> and it would figure it all out?
i.e. starting with croc 1.0.0
abra recipe release --minor --rc croc creates 1.1.0-rc1 tag then
abra recipe release --rc croc creates 1.1.0-rc2, 1.1.0-rc3 etc depending how many times you run it
abra recipe release croc creates 1.1.0

> I think the current logic of abra would simply publish -rc tags in the versions listing for each recipe yeah that's what i'm thinking too. I think we should have a `--rc` switch for `abra recipe release` but i'm not sure how to implement it. maybe you'd do `abra recipe release --minor --rc <app>` for the first rc and then `abra recipe release --rc <app>` for the following rc's and when you're ready to release the stable version `abra recipe release <app>` and it would figure it all out? i.e. starting with croc 1.0.0 `abra recipe release --minor --rc croc` creates 1.1.0-rc1 tag then `abra recipe release --rc croc` creates 1.1.0-rc2, 1.1.0-rc3 etc depending how many times you run it `abra recipe release croc` creates 1.1.0

decentral1se commented

2021-11-09 15:57:01 +00:00

Sounds good! --rc generating and maintaining the -rc<n> value seems handy to do.

Sounds good! `--rc` generating and maintaining the `-rc<n>` value seems handy to do.

decentral1se commented

2021-11-11 17:09:41 +00:00

coop-cloud/abra#123 got done, changing issue title to reflect focus on recipes now.

https://git.coopcloud.tech/coop-cloud/abra/pulls/123 got done, changing issue title to reflect focus on recipes now.

decentral1se changed title from ~~Support release candidate releasing/tagging~~ to Support RC releases for recipes

2021-11-11 17:10:08 +00:00

knoflook was unassigned by decentral1se

2021-11-11 17:11:13 +00:00

decentral1se removed this from the Beta release (software) project 2021-11-11 17:11:19 +00:00

decentral1se removed the due date 2021-11-14

2021-11-22 20:35:25 +00:00

Sign in to join this conversation.

No Milestone

No project

No Assignees

2 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: coop-cloud/organising#241