Hi all,
my thoughts:
- The structure is a bit confusing: Preparing things to do the release
and then the article sends you back to develop to update dependency.
- The article reads like releasing is a lot of manual work for building
and staging. Can't this be automated via GitHub Actions pipeli
Any comments about it?
On Sat, 11 Jan 2025 at 14:15, Slawomir Jaranowski
wrote:
>
> Hi,
>
> We should update a release procedure [1]
>
> One question, we have:
> "all issues should be assigned to responsible person, which fixed or merged
> fix"
>
> Should be the same for GitHub issues and PR?
>
