Inform about new release notes before a new release. #540
Labels
No Label
abra
abra-gandi
awaiting-feedback
backups
bug
build
ci/cd
community organising
contributing
coopcloud.tech
democracy
design
documentation
duplicate
enhancement
finance
funding
good first issue
help wanted
installer
kadabra
performance
proposal
question
recipes.coopcloud.tech
security
test
wontfix
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coop-cloud/organising#540
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I just stumbled across a never released release note (
release/next
) inside the wordpress recipe.How should we handle situation when a recipe is changes and this change requires a release note but this change/commit is not part of a release. Me and some others place the file
release/next
in the recipe to remind that this note should be included in the next release. But this file can easily be overlooked.I would propose that abra either informs about this release note during
abra recipe release
or directly renames this file with the correct version tag.Either of these seems fine. As well / instead, what about showing "unknown" release notes during
abra app upgrade
?