Medium decision: abra 1.0 release final features #670

New Issue

decentral1se · 2025-01-09T09:41:59Z

decentral1se commented

2025-01-09 09:41:59 +00:00

Just chatting with @kawaiipunk we want to prioritise stability over features. What are the things we need to finalise to bring abra to a 1.0 release? We want to bring this to a medium decision and have collective input. This is a placeholder ticket so we don't forget.

Just chatting with @kawaiipunk we want to prioritise stability over features. What are the things we need to finalise to bring `abra` to a 1.0 release? We want to bring this to a medium decision and have collective input. This is a placeholder ticket so we don't forget.

👍 1 ❤️ 2

decentral1se added the

labels 2025-04-03 08:03:48 +00:00

decentral1se added this to the Federation project 2025-04-20 06:03:06 +00:00

decentral1se moved this to Backlog in Federation on 2025-04-20 06:05:13 +00:00

decentral1se moved this to Backlog in Federation on 2025-06-04 16:21:34 +00:00

decentral1se commented

2025-10-31 14:00:40 +00:00

A mix of what I'm hearing and what I'd want to see:

Maintainers proposal implemented (@3wordchant)
The catalogue handling split out of abra (me, source)
Some optimisation work to speed up abra, aka "Make It Work, Make It Right, Make It Fast" (me)
I think the UI of abra for large collectives (cough, cough, Local-IT) is just not working and needs some serious work. abra app ls is not useful and other commands maybe too. This might need a UI/UX report. It's very tedious work also, so I'm not sure how much work we should put in here. (me)
The feature requests on the current abra "next" are pretty high in demand, I believe, including making large improvements to the recipe release process

A mix of what I'm hearing and what I'd want to see: * Maintainers proposal implemented (@3wordchant) * The catalogue handling split out of abra (**me**, [source](https://git.coopcloud.tech/toolshed/almanac)) * Some optimisation work to speed up `abra`, aka "Make It Work, Make It Right, Make It Fast" (**me**) * I think the UI of `abra` for large collectives (*cough*, *cough*, Local-IT) is just not working and needs some serious work. `abra app ls` is not useful and other commands maybe too. This might need a UI/UX report. It's very tedious work also, so I'm not sure how much work we should put in here. (**me**) * The feature requests on the current [`abra` "next"](https://git.coopcloud.tech/toolshed/-/projects/41) are pretty high in demand, I believe, including making large improvements to the recipe release process

👍 1

3wordchant commented

2025-11-04 17:19:06 +00:00

Sounds great to me!

Only additional thing I wonder is whether we add the website relaunch? Could always have it as a "nice-to-have" to avoid it blocking everything else… but maybe a shiny 1.0 package could be motivating to us all?

Sounds great to me! Only additional thing I wonder is whether we add the website relaunch? Could always have it as a "nice-to-have" to avoid it blocking everything else… but maybe a shiny 1.0 package could be motivating to us all?

👀 1 ❤️ 1

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: toolshed/organising#670

Medium decision: abra 1.0 release final features #670

Medium decision: `abra` 1.0 release final features #670