镜像站点 · 本页由第三方 GitHub 只读镜像提供,非 GitHub 官方站点,不接受任何登录或凭据输入。前往 github.com
Skip to content

Release proposal: v1.6.0 #1157

Description

@rvagg

We're starting to need a new release but we're in an awkward position of not having a good story around a semver-minor bump and there's a few issues & PRs in flux that would be good to get resolved before a release.

Note in the commit list below, the commit from #881 was reverted so no longer applies, but its resolution may be at hand so it can come back in. This would help with a 1.6.0 justification.

Also for those interested in semver arguments, please head over to #1116 and see what you think about it being semver-minor or semver-patch. It's the only thing in here that's warranting the bump to 1.6. If it wasn't for this addition then I'd have just pushed for a quick 1.5.2 and be done with this batch of commits.

So, I'm proposing a holding pattern for this release for up to 3 days to see if we can get some meat in here. Some issues worth monitoring are:

Activity

  1. Fishrock123 commented on Mar 14, 2015

    @Fishrock123
    Contributor

    ahhh ya beat me to it, I decided to hold off until tomorrow haha

    👍

  2. piscisaureus commented on Mar 14, 2015

    @piscisaureus
    Contributor

    [7bde3f1] - (SEMVER-MINOR) src: add -r/--require flags for preloading modules (Ali Ijaz Sheikh)

    This patch has been reverted for now I thought?

  3. rvagg commented on Mar 14, 2015

    @rvagg
    MemberAuthor

    yep

    [056ed4b] - src: revert -r/--require flags (Chris Dickinson) #1150

  4. mikeal commented on Mar 14, 2015

    @mikeal
    Contributor

    This should probably be a semver-major change if accepted (I don't think it will be, that issue seems to be going another way).

  5. brendanashworth commented on Mar 16, 2015

    @brendanashworth
    Contributor

    A good reason for semver-minor could be #1156

  6. bnoordhuis commented on Mar 16, 2015

    @bnoordhuis
    Member

    Another one: #1162

  7. cjihrig commented on Mar 16, 2015

    @cjihrig
    Contributor

    Another semver minor: #1163. Specifically, 095ae0d.

  8. jameshartig commented on Mar 16, 2015

    @jameshartig
    Contributor

    Since 095ae0d is my commit, I'm not sure if I should chime in or not but its just making socket*() return the ip/port used even after the socket is closed. Before that commit, if the socket was closed, socket*() methods would return null.

  9. bnoordhuis commented on Mar 16, 2015

    @bnoordhuis
    Member

    @fastest963 I suggested semver-minor because it can break code that uses e.g. socket.remotePort === undefinedas an indicator of whether the socket is connected.

  10. jameshartig commented on Mar 16, 2015

    @jameshartig
    Contributor

    @bnoordhuis thanks for the clarification. Makes sense.

  11. rvagg commented on Mar 17, 2015

    @rvagg
    MemberAuthor

    will try and get this out tomorrow, then I guess we'll have 1.6.1 to do in a couple of days after that thanks to openssl.

  12. shigeki commented on Mar 18, 2015

    @shigeki
    Contributor

    @rvagg Your CI of 317 was deleted and my job had an error as https://jenkins-iojs.nodesource.com/job/iojs+any-pr+multi/318/console . Is there something wrong on CI?

  13. jbergstroem commented on Mar 18, 2015

    @jbergstroem
    Member

    @shigeki yeah, so it seems :-/

  14. 18 remaining items

  15. chrisdickinson commented on Mar 19, 2015

    @chrisdickinson
    Contributor

    Release commit is authored. Editing the markdown out is kind of a slog – anyone have a better solution?

  16. chrisdickinson commented on Mar 19, 2015

    @chrisdickinson
    Contributor
  17. chrisdickinson commented on Mar 19, 2015

    @chrisdickinson
    Contributor

    OSX build has finished. Tested against hapi on v10.10, works.

  18. chrisdickinson commented on Mar 19, 2015

    @chrisdickinson
    Contributor

    Windows 2008 x64 has finished. Tested against hapi on windows 7. Some test failures (looks like it was sniffing for error messages!)

  19. chrisdickinson commented on Mar 19, 2015

    @chrisdickinson
    Contributor

    Looks like our ARM friends have hung. Proceeding to promote others, will circle back on ARM builds later.

  20. chrisdickinson commented on Mar 19, 2015

    @chrisdickinson
    Contributor

    Done. cc @Fishrock123, we should be good to go.

  21. Fishrock123 commented on Mar 19, 2015

    @Fishrock123
    Contributor

    Website updated: nodejs/iojs.org@8a6bb34

  22. jbergstroem commented on Mar 19, 2015

    @jbergstroem
    Member

    Great job all 🎉

  23. feross commented on Mar 19, 2015

    @feross
    Contributor

    Looks like we might need a quick 1.6.1 to fix this bug: #1208

  24. rvagg commented on Mar 20, 2015

    @rvagg
    MemberAuthor

    @chrisdickinson the arm builds for 1.6.0 are ready to promote, would you mind bumping those with tools/release.sh

  25. chrisdickinson commented on Mar 20, 2015

    @chrisdickinson
    Contributor

    @rvagg sorry, I dropped the ball on the arm builds. OK to run this now?

  26. rvagg commented on Mar 20, 2015

    @rvagg
    MemberAuthor

    @chrisdickinson yep, should be, first time we've had overlap like this so I'm keen to see if it works as planned!

  27. chrisdickinson commented on Mar 20, 2015

    @chrisdickinson
    Contributor

    Seems to have worked!

  28. added
    metaIssues and PRs related to the general management of the project.
    on Mar 25, 2015
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

    metaIssues and PRs related to the general management of the project.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions