docs: Maintainers let's goooo #48

Merged
3wordchant merged 1 commits from docs/3wc/putting-together-a-team into main 2026-05-07 15:51:44 +00:00
Owner

Closes: #38

Closes: #38
3wordchant added 1 commit 2026-04-27 18:18:35 +00:00
docs: Maintainers let's goooo
Some checks failed
continuous-integration/drone/pr Build is failing
35280b714b
3wordchant requested review from benjaminlyng 2026-04-27 18:18:35 +00:00
3wordchant requested review from nicksellen 2026-04-27 18:18:35 +00:00
Owner

Ah nice, good effort!

Ah nice, good effort!
nicksellen approved these changes 2026-04-27 19:35:05 +00:00
nicksellen left a comment
Owner

I'm happy with that. I wonder what happens if we don't meet the timescales mentioned?

The other part I wonder about is (I think I wrote about it too somewhere?) when to write the release note (as you ideally need to know the version number, which isn't detirmined in the PR?), so more generally, how is the release process triggered in relation to merging PRs.

(Sorry, if my comment is a bit rambling, in a hurry!!!)

I'm happy with that. I wonder what happens if we don't meet the timescales mentioned? The other part I wonder about is (I think I wrote about it too somewhere?) when to write the release note (as you ideally need to know the version number, which isn't detirmined in the PR?), so more generally, how is the release process triggered in relation to merging PRs. (Sorry, if my comment is a bit rambling, in a hurry!!!)
Owner

@nicksellen you can create and add notes to release/next and abra recipe release will rename that for you when you're choosing the new release version (docs). The release process changed slightly and we're still trying to figure out how to adjust it for PR review / merge / release workflow in toolshed/abra#806. So, it's still a bit of a moving target, thoughts welcome once you get back into it!

@nicksellen you can create and add notes to `release/next` and `abra recipe release` will rename that for you when you're choosing the new release version ([docs](https://docs.coopcloud.tech/maintainers/handbook/#how-do-i-write-version-release-notes)). The release process changed slightly and we're still trying to figure out how to adjust it for PR review / merge / release workflow in https://git.coopcloud.tech/toolshed/abra/issues/806. So, it's still a bit of a moving target, thoughts welcome once you get back into it!
3wordchant merged commit f2f7b05c82 into main 2026-05-07 15:51:44 +00:00
3wordchant deleted branch docs/3wc/putting-together-a-team 2026-05-07 15:51:44 +00:00
Sign in to join this conversation.
No Label
3 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: coop-cloud/mastodon#48
No description provided.