Skip to content

Complete steps needed to get out of experimental #284

Closed

Description

@mhdawson

Activity

  1. added this to the Milestone 9 milestone on Oct 12, 2017
  2. changed the title [-]Complete steps need to get out of experimental[/-] [+]Complete steps needed to get out of experimental[/+] on Oct 26, 2017
  3. aruneshchandra commented on Dec 5, 2017

    @aruneshchandra
    Contributor

    The group agreed on the following criteria to exit experimental status:

    Criteria Status
    Multiple implementations of n-api on at least 2 VMs Done
    Define N-API / async_hooks dependency Done #14697
    At least two modules used in real world use cases on at least one VM In progress. bcrypt, weak-napi and iotivity-node (used in academic project "Campie")
    At least two modules that are NPM installable with pre-builds and all unit tests passing We should continue to enable this, but it does not have any impact on the stability of N-API. Next step is to discuss with TSC to remove this as a blocking criterion
  4. aruneshchandra commented on Dec 14, 2017

    @aruneshchandra
    Contributor

    Pre-gyp conversations is on issue #263

  5. aruneshchandra commented on Mar 1, 2018

    @aruneshchandra
    Contributor

    node-zopfli is now being used in production with Edge Dev portal on Node-ChakraCore

  6. mhdawson commented on Mar 5, 2018

    @mhdawson
    MemberAuthor

    Issue with request to move out of experimental: nodejs/TSC#501

  7. mhdawson commented on Apr 12, 2018

    @mhdawson
    MemberAuthor

    Closing, out of experimental in master.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions