Skip to content
This repository has been archived by the owner on Mar 25, 2018. It is now read-only.

How to inform community about known breakages #31

Closed
MylesBorins opened this issue Feb 18, 2016 · 4 comments
Closed

How to inform community about known breakages #31

MylesBorins opened this issue Feb 18, 2016 · 4 comments

Comments

@MylesBorins
Copy link

How can we do a better job at this?

@yoshuawuyts
Copy link

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
Copy link
Member

rvagg commented Feb 18, 2016

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

@thefourtheye
Copy link

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

@mikeal
Copy link
Contributor

mikeal commented Feb 18, 2016

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants