Skip to content

Release plan for v4 / v6 until April 2017 #159

Closed

Description

@MylesBorins

We are planning monthly releases on the first Tuesday of every month for v4 and v6, and a single v0.12 release in the first week of December. Currently our only planned Semver-Minor release if v4.7.0 on December 6th, but it is possible that one of the patch releases on v4 or v6 could be a minor release if deemed necessary by the LTS Working Group. These dates are also subject to change based on the need for security releases.

February 21st

Release of v4.8.0 and v6.10.0

March 21st

Release of v4.8.1 and v6.10.1

Activity

  1. MylesBorins commented on Nov 16, 2016

    @MylesBorins
    ContributorAuthor

    Please let me know if you have problems with the dates above. I would also be interested if individuals think the information above could be presented in a clearer fashion. I'm also interested if individuals think that the above information should be present in the repo's readme.

  2. AdriVanHoudt commented on Nov 18, 2016

    @AdriVanHoudt

    Can it be visualised on the current (most used?) LTS visualisation from Nodesource?

  3. rvagg commented on Nov 19, 2016

    @rvagg
    Member

    @AdriVanHoudt that might give the impression that these dates are more concrete than they are, there's a bunch of factors that could easily change these plans, most notably security releases which could change version numbers and bump dates if they are too close.

  4. AdriVanHoudt commented on Nov 19, 2016

    @AdriVanHoudt

    @rvagg good point, it was just my initial thought on could be presented in a clearer fashion but you are right if they are not final it probably just a case of where to put the info

  5. MylesBorins commented on Dec 7, 2016

    @MylesBorins
    ContributorAuthor
  6. hutson commented on Dec 8, 2016

    @hutson
    Contributor

    In that case, I find the formatting of the dates in the original issue comment to be readable, and this issue to be sufficient; with the caveat that it would be helpful if the issue's original comment is kept up-to-date (so that I do not need to parse the entire thread to grasp the current state of your release plans).

  7. MylesBorins commented on Dec 8, 2016

    @MylesBorins
    ContributorAuthor
  8. richardlau commented on Jan 5, 2017

    @richardlau
    Member

    @MylesBorins Maybe update the first comment to take into account the point releases made earlier today?

  9. changed the title [-]Release plan for v0.12 / v4 / v6 until April 2017[/-] [+]Release plan for v4 / v6 until April 2017[/+] on Jan 6, 2017
  10. MylesBorins commented on Jan 6, 2017

    @MylesBorins
    ContributorAuthor

    @richardlau good call!

  11. mhdawson commented on Mar 14, 2017

    @mhdawson
    Member

    @MylesBorins should we be adding the schedule for the next 2 releases as well ? Possibly:

    April 24th

    Release of v4.9 (as Quarterly semver minor starting off Maintenance phase) and v6.11

    May 23rd

    Release v6.11.1

  12. MylesBorins commented on Mar 14, 2017

    @MylesBorins
    ContributorAuthor

    @mhdawson based on the schedule v4 is moving to maintenance mode as of April 1st. We just did a semver minor last month, so I think it is a bit soon to do the minor for v6.

    I'll put together a new issue for our Q2 release schedule next week

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