Skip to content

Next release checklist #256

Closed
Closed
Next release checklist#256

Description

@tbranyen
tbranyen
opened on Oct 26, 2014
  • Update scripts in example folder.
  • Changelog and migration notes.
  • Ensure all existing tests are passing (no skips allowed).

... I'll update this when I think of more things. Feel free to comment if you think I've missed something.

Activity

  1. johnhaley81 commented on Oct 26, 2014

    @johnhaley81
    johnhaley81
    on Oct 26, 2014
    Collaborator

    Are we looking to get the async callback stuff in for the next release?

  2. tbranyen commented on Nov 21, 2014

    @tbranyen
    tbranyen
    on Nov 21, 2014
    MemberAuthor

    all the test are passing, but have that one skip, need to investigate how to properly set --expose-gc

  3. maxkorp commented on Nov 21, 2014

    @maxkorp
    maxkorp
    on Nov 21, 2014
    Collaborator

    I dunno how we want to write it up, but I'd like to get most of the core functionality implemented. Not convenience on top (that can come later) but I think while we're running around declaring "ALL IS BREAKY! RIP LEGACY" we ought to get the brunt of it functional.

  4. johnhaley81 commented on Nov 21, 2014

    @johnhaley81
    johnhaley81
    on Nov 21, 2014
    Collaborator

    What about the --expose-gc flag for node?

  5. maxkorp commented on Nov 24, 2014

    @maxkorp
    maxkorp
    on Nov 24, 2014
    Collaborator

    gonna write up some migration notes and the change log.

  6. tbranyen
    closed this as completedon Nov 25, 2014
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