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!!!)
@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!
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.
Closes: #38
Ah nice, good effort!
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!!!)
@nicksellen you can create and add notes to
release/nextandabra recipe releasewill 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!