Re: [Csnd-dev] [EXTERNAL] [Csnd-dev] Feedback on Automating Csound Releases
Rory Walsh <[email protected]>
| Newsgroups | gmane.comp.audio.csound.devel |
|---|---|
| Message-ID | <CAMJR=HMfK5SzpQy8RZG7P3Ndh+qBiBE9AVdApPx1zGh3aORYaA@mail.gmail.com> |
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 > >