[QUESTION] releases vs tags about stackql HOT 10 CLOSED

@iMichka thank you for reaching out. From our point of view, we want to release often and have the latest available to all users. It is better if you aggressively update homebrew. Unfortunately we are pretty slow with releasing via git etc, due to some manual stuff. Full disclosure I don't know anything about brew bump; is there anything we can do to make this easier or configure our formula to clarify what is desirable?

from stackql.

No need for brew bump: we check at least daily if there is an update on your repo, and will update the package accordingly. It's automatised. There are ways to push the releases from your side to homebrew (in case you want to get things shipped really really fast).

The issue we have right now is that there is a mismatch between this page https://github.com/stackql/stackql/releases, that defines the last release, and the two last tags. We have projects that will use tags as "beta" versions, or even move tags around (which is bad). This is why we prefer releases on top of tags. And we are often worried when we see new tags appear, but no new release.

from stackql.

hi @iMichka we are happy with releases, we generally create a stable release from tags once a month or so, although there may be one or more PRs to main and tagged builds in between, we create the releases manually and then add artifacts to the release (like Signed Windows MSI packages and MacOS notarized PKG files), we then create Chocolatey packages separately through another process, this is all semi-automated (scripted but manually triggered). Long story short, happy to use new releases to create new Homebrew packages if that's what you prefer.

from stackql.

It depends on what you prefer: do you want us to ship releases, or each single tag (even if there is no associated release) ?

from stackql.

lets do releases @iMichka

from stackql.

@jeffreyaven thanks for clarifying, can you generate the release notes for both v0.5.589 and v0.5.591 tags? Once that is done, we (homebrew) can just ship this PR out

from stackql.

Hi @chenrui333, Ill create a release for v0.5.591 and generate release notes later today (wont bother with v0.5.589, let you know when its ready

from stackql.

yeah, thanks @jeffreyaven! 🙏

from stackql.

here you go @chenrui333 v0.5.591

from stackql.

Thanks, i guess this can be closed via Homebrew/homebrew-core#165656

from stackql.