Rename abra recipe upgrade #953

New Issue

2026-10-17T18:27:33Z

iexos commented

2026-10-17 18:27:33 +00:00

There is still confusion with the recipe upgrade workflow. One thing we can do about it is of course better documentation. Another though is that the different purposes of recipe upgrade and recipe release aren't immediately obvious.

I suggest we rename recipe upgrade to something which clarifies its purpose, e.g.:

abra recipe upgrade-images
abra recipe upgrade-image-tags
abra recipe fetch-image-tags
...

You get the idea, naming suggestions welcome :)

There is still confusion with the recipe upgrade workflow. One thing we can do about it is of course better documentation. Another though is that the different purposes of `recipe upgrade` and `recipe release` aren't immediately obvious. I suggest we rename `recipe upgrade` to something which clarifies its purpose, e.g.: - `abra recipe upgrade-images` - `abra recipe upgrade-image-tags` - `abra recipe fetch-image-tags` - ... You get the idea, naming suggestions welcome :)

decentral1se added the enhancement label 2026-10-19 08:58:31 +00:00

decentral1se commented

2026-10-19 09:01:26 +00:00

There is still confusion with the recipe upgrade workflow.

What kind of confusion? Do you have quotes or links?

Renames need to have wide agreement with a consensus that it will improve the situation beforehand. Otherwise, you risk going into the exact same problem you had before with a new group of people who are confused.

Btw, you can patch abra with a synonym on upgrade which maintains backwards compatibility with upgrade while allowing $whatever_else if you want to test stuff out practically.

> There is still confusion with the recipe upgrade workflow. What kind of confusion? Do you have quotes or links? Renames need to have wide agreement with a consensus that it will improve the situation beforehand. Otherwise, you risk going into the exact same problem you had before with a new group of people who are confused. Btw, you can patch `abra` with a synonym on `upgrade` which maintains backwards compatibility with `upgrade` while allowing `$whatever_else` if you want to test stuff out practically.

iexos commented

2026-10-22 16:18:47 +00:00

Hm just some general comments in chat that made me think about my initial confusion. Its more of an idea how to make things more clear as upgrade feels ambiguous in this context. And it might not be worth the trouble... So its fine for me to close this.

Hm just some general comments in chat that made me think about my initial confusion. Its more of an idea how to make things more clear as `upgrade` feels ambiguous in this context. And it might not be worth the trouble... So its fine for me to close this.

decentral1se commented

2026-10-23 08:05:05 +00:00

Let's keep it open and see where the conversation goes.

"The refactoring will continue until moral improves"

😆

Let's keep it open and see where the conversation goes. "The refactoring will continue until moral improves" 😆

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: toolshed/abra#953

Rename abra recipe upgrade #953

Rename `abra recipe upgrade` #953