Adding tags/releases to the repository about epic-stack HOT 6 CLOSED

I think a good way to mark releases would be anytime features are added/removed, core dependencies are updated *@remix-run/*, react, react-dom, etc). This allows a fairly regular version cycle without it being tied to a schedule.

from epic-stack.

Ok, I think I can create releases occasionally for significant changes (stuff I've been using announcements for in discussions). But I won't make a release if I'm just updating package.json or fixing a typo.

Thanks!

from epic-stack.

Would we just make a tag for every commit? I just don't know how to version this in a way that's more helpful than the commit history.

from epic-stack.

I think there's different ways you could go about it. One could be every to tag commit but I guess that's the same as commit history, another one could be to tag just the updates to the libraries, that way you could easily link packages versions to the version of epic stack.

But if it were me, I think I'd go for something like scheduled releases and treat anything in between as "pre-releases" or something like that. That way you get a cadence for releases which makes it predictable for users of the stack and also it becomes something that doesn't interfere too much with the current workflow (this is an assumption ofc).

Something like quarterly tags/releases feels about right since it's not that big of a time period to allow big major upgrades accumulate too much but also it's not that small of a time period to make the whole thing become too similar to just watching the commit history. It'd also be easier to do partial upgrades. Like instead of updating to the latest and greatest, you could choose a tag that might not be the latest but comes close to it or solves some critical security issue.

Hopefully my ideas make sense to everyone 🤞🏼

from epic-stack.

Hi,

I really like your proposition.
One way, we could do that is by adding changesets.
This will add a Changelog and make it easier to create tags / release.

Ideally, each commit on main should contain a changeset file, it won't disturb too much the current workflow and when there is significant changes, Kent can create a release.

What do you think ?

from epic-stack.

I think a good way to mark releases would be anytime features are added/removed, core dependencies are updated *@remix-run/*, react, react-dom, etc). This allows a fairly regular version cycle without it being tied to a schedule.

I like this idea 👍

from epic-stack.