nodejs / NG

Next Generation JavaScript IO Platform
103 stars 12 forks source link

How to inform community about known breakages #31

Closed MylesBorins closed 7 years ago

MylesBorins commented 8 years ago

How can we do a better job at this?

yoshuawuyts commented 8 years ago

This is for new bugs popping up right? (e.g. to be fixed)

Perhaps something like status.github.io but for Node could work - list the latest releases / LTS versions and known bugs / failures. Could come in handy for linking back to from tweets and stuff - I reckon it might be better on the eyes than linking to GitHub issues. What do you reckon?

rvagg commented 8 years ago

that could be pretty easily achieved with labels, and our collaborator army is pretty awesome with applying labels

thefourtheye commented 8 years ago

semver-major tag should be a good indicator, no?

mikeal commented 8 years ago

This should probably go on the roadmap or evangelism repo depending on how you see it playing out. This is something that is actionable today so it doesn't need to be in NG.