Re: [Csnd-dev] [EXTERNAL] [Csnd-dev] Feedback on Automating Csound Releases

This introduces a release pipeline by adding the tag release. Could you add
a documentation for this new behaviour in your PR for other maintainers to
understand how this works and what happens. Also if the tagging release
involves using conventional commits, this should be documented too ( I am
in favour of conventional commits ).
maybe add it here?
https://github.com/csound/csound/tree/develop/doc/RELEASING.md

On Mon, 21 Jul 2025 at 11:42, Victor Lazzarini <
[email protected]> wrote:

> Thanks a lot for this!
>
> Prof. Victor Lazzarini
> Maynooth University
> Ireland
>
> On 21 Jul 2025, at 03:37, Werner Mendizabal <[email protected]>
> wrote:
>
> 
>
> Hello fellow Csound developers,
>
> I’ve opened a PR that introduces automated versioning and publishing of
> Csound releases: https://github.com/csound/csound/pull/2206
>
> With this workflow, when a PR is merged and the release label is added, a
> new GitHub release will be automatically created.
> Additionally, PRs labeled as enhancement or bug will be categorized
> accordingly in the autogenerated release notes.
>
> Feel free to take a look and let me know if you have any feedback or
> questions!
>
> Best regards,
> - Werner
>
> On Tue, Mar 4, 2025 at 5:41 AM Rory Walsh <[email protected]> wrote:
>
>> I don't think pushing a new beta on each dev merge is that big a deal as
>> long as we only retain the last 2 or 3 builds.
>>
>> On Sat, 1 Mar 2025 at 19:24, Victor Lazzarini <
>> [email protected]> wrote:
>>
>>> Thanks for this, I think this is really helpful.
>>>
>>> It looks like the right thing. We can do the betas and when the time
>>> comes, the full release.
>>>
>>> One of my main concerns is to have the whole mechanism documented so
>>> everyone working on the project knows the score.
>>>
>>> One thing we could do is to have a beta-release branch so that we don't
>>> necessary make releases at every develop update.
>>>
>>>
>>> Prof. Victor Lazzarini
>>> Maynooth University
>>> Ireland
>>>
>>> On 1 Mar 2025, at 18:23, Werner Mendizabal <[email protected]>
>>> wrote:
>>>
>>> 
>>> *Warning*
>>>
>>> This email originated from outside of Maynooth University's Mail System.
>>> Do not reply, click links or open attachments unless you recognise the
>>> sender and know the content is safe.
>>>
>>> Hello Csound developers,
>>>
>>> I’m planning to submit a pull request to automate the creation of Csound
>>> releases when merging into the development branch.
>>>
>>> Before proceeding, I’d like to get your feedback on whether an
>>> implementation similar to my own project would be acceptable.
>>>
>>> For reference, here are the releases for my project: Godot-Csound
>>> Releases <https://github.com/nonameentername/godot-csound/releases>.
>>> The release notes are automatically generated based on a GitHub release
>>> file
>>> <https://github.com/nonameentername/godot-csound/blob/main/.github/release.yml>
>>> .
>>>
>>> Key features of this approach:
>>>
>>>    - Commits tagged with "feature" or "bug" are categorized accordingly
>>>    in the release notes.
>>>    - The anothrNick/github-tag-action
>>>    <https://github.com/anothrNick/github-tag-action> GitHub Action is
>>>    used to automatically tag releases.
>>>    - Most of the release process is automated, simplifying version
>>>    management.
>>>
>>> Please let me know if you have any questions or suggestions.
>>>
>>> Thanks,
>>>     Werner
>>>
>>>