search

w3c / spec-prod

GitHub Action to build ReSpec/Bikeshed specs, validate output and publish to GitHub pages or W3C
https://w3c.github.io/spec-prod/
MIT License
34 stars 21 forks source link

Use bikeshed version from github rather than pip #90

Closed dontcallmedom closed 3 years ago

dontcallmedom commented 3 years ago

Since the releases from bikeshed to pip aren't automated, there can be a gap between fixes brought to boilerplate files landed on github, and their availability through spec-prod (which uses the pip version of bikeshed).

To avoid that delay and reduce the confusion it creates (as e.g. in #83 and more recently for myself with webnn), I think it would be best if spec-prod were to use the latest version of bikeshed from github rather than pip.

sidvishnoi commented 3 years ago

See https://github.com/w3c/spec-prod/issues/59#issuecomment-839531265

jyasskin commented 3 years ago

@tabatkins probably has opinions here. I believe the pip releases are helpful in increasing stability.

tabatkins commented 3 years ago

What I really need to do is decouple the boilerplates from the code updates, so they can be received by a bikeshed update and I don't have to push new pip versions for them. It's on my plate of things to do near-term.

So I recommend just sticking with pip for code stability, and waiting for me to do this decoupling.

dontcallmedom commented 3 years ago

with bikeshed 3.1 available on pip and featuring autonomous boilerplate, I think this issue can be closed as overtaken by events.