Tools: ☂️ Published Release

[sebmck]

This issue is to track the milestone Published Release.

Rome is still in development and once we are confident we have something usable and stablefor a wider audience we'll publish to npm.

[wzalazar]

all packages will have the same version when you publish or will be independent?

[sebmck]

The only package that will be published will be packages/rome. All the others are just for internal organization.

[wzalazar]

So, Do you consider implement semantic release for that?

[macovedj]

Looks like there's already a rome on npm. Do you know yet how you plan to handle that?

[sebmck]

@macovedj I'm the owner of that package. @bevacqua graciously donated it! :heart:

[diokey]

Are you targeting a particular timeline for the release or is it just whenever things are ready?

[sebmck]

When things are ready. Unclear what that actually means. I can guarantee a release by the end of the month though, even if it's not ready we'll still publish to npm and figure out the remaining gaps.

[mattcompiles]

Feel like changesets would be a good option for Rome to keep track of release notes over time.
https://github.com/atlassian/changesets

[sebmck]

I'm going to be making another issue to track this.