What is the criteria and plan for the next release?

[chebread]

I have a question regarding the release process for devd.

With the recent PRs successfully merged (fixing localhost routing, updating Go modules, etc.), the codebase has been significantly improved. I am curious about what the criteria are for cutting a new release.

I am cautious about proposing a new release directly. However, in my personal opinion, devd is currently in need of a new release so that users can actually benefit from these recent improvements, rather than being stuck on the old v0.9 binaries.

Could you share how the timing for a new release is typically decided for this project?

[wader]

Agree, it would be nice with a new release once we merge most of the maintenance stuff. Maybe should figure out a release build plan also? https://goreleaser.com, something else or just "manual" script in github actions that builds various binaries and copy artifacts?

[llimllib]

I've had great success with goreleaser, I've been using it in https://github.com/llimllib/git-ls for example, can strongly recommend it.

I'd be happy to set it up for you if you'd like, I already have my own fork of devd from a long time ago and can help in general if you'd like.

[chebread]

@llimllib I have already completed the PR for CI/CD using goreleaser. The point this issue raises is how future versions of devd will be handled. Did you understand what I just said?

[llimllib]

Apologies for irritating you, I guess!

[wader]

@chebread did you end up finding any alternative you like more?

[chebread]

Apologies for irritating you, I guess!

@llimllib, I was not offended at all !! I only informed you because you misunderstood the issue.

[chebread]

It's been a really long time, @wader. I think that as long as we don't leave GitHub, goreleaser fits GitHub Actions best currently.

[wader]

I think that is fine. Want to revive #135 ? i emailed a bit with @cortesi earlier this week so now appveyor is gone. But i guess we still will need help from him to generate a access token secret that can publish releases?

[thediveo]

Any movement on this please? It would simplify things for my devcontainer feature (focuses on serving docsify content) if fresh releases for linux/amd64 and linux/arm64 binaries would be available.