<@492751562872193025> or <@138354902966599681> ha...
# avo-2
s
@lemon-wall-20836 or @loud-jewelry-99127 have you all documented the release cycle? I remember Adrian said it in a video somewhere, but it's not clear when releases are occurring. I'm less worried about big features, but when there are small bugfixes (that limit the ability to upgrade to newly released features) two weeks seems like a long time to wait for new gem to be cut.
l
We release every two weeks on Tuesday. https://github.com/avo-hq/avo/blob/main/RELEASE.MD
I’m AFK right now
Usually how we did it was like this: if there’s a critical bug after a release, we’d fix it soon (a few hours/first, second day) and release a patch version or a prerelease so you can continue using it until we merge it to main and release a major version
This for example
s
Right. But https://github.com/avo-hq/avo/pull/1213 is an example: merged 7 days ago and I don't see a minor gem release. I wonder if a nice thing to do would be a "ship a patch version" with every main change.
Again, not complaining. It'd just be nice.
l
yeah, I see what you mean
usually, I'm all for daily releases
the bi-weekly schedule is just something to mark a "milestone"
I stopped doing the weekly releases because they take a lot of time to put together, shoot the screencast, and announce everywhere
another thing that I do is to publish a pre-release on request. Like, if you need that feature sooner, rather than later, send a comment on the PR and I'll cut a release there
does that sound ok?
s
Happy to request cutting a gem - I'd just prefer not to add work to your plate as there are many things you're juggling. Bi-weekly releases (with video + write up + promo) is awesome and weekly seemed highly unsustainable/not good for the project long term. I'm just imaging a Github action that on a pr merge, auto-publishing a gem version could be something like
2.1.1-sha
too. The biggest problem with this project (that isn't really a big problem at all) is that you can't just point your Gemfile to the github main branch and get a good result. Perhaps I need to brush those directions off you sent me many moons ago.
l
I'll add instructions on how to use a specific github branch/commit
it's just the assets that need to be built
thanks for the feedback!
I'll add those instructions today or tomorrow the latest
s
Thanks Adrian. You're killin' it!
5 Views