rename this repo to `ses-shim` ?

We’re planning to retire https://github.com/Agoric/SES , in favor of this repo. Obviously we need to remove the -beta from the name. @erights @dtribble any objections to naming it https://github.com/Agoric/ses-shim ?

(note that we’ve used that name for this repo in the past, before renaming it to SES-beta, so if you visit that URL, you’ll be redirected back here)

[jfparadis]

Great.

1. I like ses-shim: it is the SES repo as in git clone <something>ses-shim.git
2. I like the npm package ses. It is also the ses path in the monorepo ./packages/ses That was the intention to avoid confusion between the two.

Let’s do this for version:

• This SES is too big of a change to be called a minor release and 0.8.0 doesn’t cut it. It’s a complete API change, and a minor just doesn’t capture that. We need to abide to the semantic:

Changes that break backward compatibility: Major release https://docs.npmjs.com/about-semantic-versioning

• Remove -beta from the git repo and add it to the version: 1.0.0-beta.0. The semantic of npm versioning allow for a prerelease. The .0 indicates the first beta. When we have a new beta, we increment the .0 to .1 and so on. https://docs.npmjs.com/cli/dist-tag
• The readme will capture the npm version and display it (it is configures to show the current version)

This is a very good read: https://medium.com/@kevinkreuzer/publishing-a-beta-or-alpha-version-to-npm-46035b630dd7

[kriskowal]

This transition appears to be completed.