search

w3c / respec-vc

Verifiable Credential extensions to ReSpec
Other
3 stars 5 forks source link

Add release process description to README. #37

Closed BigBlueHat closed 3 months ago

BigBlueHat commented 4 months ago

Figured we should document this so others can follow it in future (and improve on it eventually).

davidlehn commented 4 months ago

The pattern presented here is problematic. It is storing large built files in git history forever. This will continue to grow bloat in the source repo that is otherwise small. I suggest using a npm process. https://github.com/w3c/respec-vc/issues/4

I have access to publish packages now. Including build artifacts in the packages uploaded to npm and omitting them from source control is a common best practice. The only user difference will be a slightly different CDN URL. I think the only main issue here is it would be good to have a backup person or two with access to publish the package.

iherman commented 4 months ago

Just asked @deniak for an account, @davidlehn.

BigBlueHat commented 3 months ago

Merged this as (despite it's less than ideal nature) this is how we do it today...so it merits documentation. We can look to #4 or other for future improvement.