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

How to inform community about known breakages #31

Closed

Description

@MylesBorins

How can we do a better job at this?

Activity

  1. yoshuawuyts commented on Feb 18, 2016

    @yoshuawuyts

    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?

  2. rvagg commented on Feb 18, 2016

    @rvagg
    Member

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

  3. thefourtheye commented on Feb 18, 2016

    @thefourtheye

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

  4. mikeal commented on Feb 18, 2016

    @mikeal
    Contributor

    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 join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions