Grokbase › Groups › Go › golang-dev › December 2014
FAQ
This is just me speaking, not the Go team.

I'd like to ask what people think about shifting our release cycle to
spring and autumn rather than the current summer and winter cycles. The
problem with the current cycle is that both release dates each year happen
at inconvenient times on the calendar, with folks taking time off for
official and unofficial holidays.

The current releases are June and December. It might be easier if they
happened two or three months later (although still on the 6 month cycle),
say September and March. To do this, we'd need to have an 8 or 9 month
cycle first, but the 1.5 release is a major upheaval so it seems like a
good candidate for having a little extra time to get the bugs out.

Please let me know what you think. Again, this is not an official proposal,
just a question for now.

-rob

--
You received this message because you are subscribed to the Google Groups "golang-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.

Search Discussions

  • Andrew Gerrand at Dec 16, 2014 at 1:57 am ⇧
    This would work better around the conference schedule, too.
    On Tue, 16 Dec 2014 at 12:54, Rob Pike wrote:

    This is just me speaking, not the Go team.

    I'd like to ask what people think about shifting our release cycle to
    spring and autumn rather than the current summer and winter cycles. The
    problem with the current cycle is that both release dates each year happen
    at inconvenient times on the calendar, with folks taking time off for
    official and unofficial holidays.

    The current releases are June and December. It might be easier if they
    happened two or three months later (although still on the 6 month cycle),
    say September and March. To do this, we'd need to have an 8 or 9 month
    cycle first, but the 1.5 release is a major upheaval so it seems like a
    good candidate for having a little extra time to get the bugs out.

    Please let me know what you think. Again, this is not an official
    proposal, just a question for now.

    -rob

    --
    You received this message because you are subscribed to the Google Groups
    "golang-dev" group.
    To unsubscribe from this group and stop receiving emails from it, send an
    email to [email protected].
    For more options, visit https://groups.google.com/d/optout.
    --
    You received this message because you are subscribed to the Google Groups "golang-dev" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
    For more options, visit https://groups.google.com/d/optout.
  • Dave Cheney at Dec 16, 2014 at 1:57 am ⇧
    I have felt the same for some time.

    I support this proposal.

    Thanks for raising this.

    Cheers

    Dave
    On Tue, Dec 16, 2014 at 12:54 PM, Rob Pike wrote:
    This is just me speaking, not the Go team.

    I'd like to ask what people think about shifting our release cycle to spring
    and autumn rather than the current summer and winter cycles. The problem
    with the current cycle is that both release dates each year happen at
    inconvenient times on the calendar, with folks taking time off for official
    and unofficial holidays.

    The current releases are June and December. It might be easier if they
    happened two or three months later (although still on the 6 month cycle),
    say September and March. To do this, we'd need to have an 8 or 9 month cycle
    first, but the 1.5 release is a major upheaval so it seems like a good
    candidate for having a little extra time to get the bugs out.

    Please let me know what you think. Again, this is not an official proposal,
    just a question for now.

    -rob

    --
    You received this message because you are subscribed to the Google Groups
    "golang-dev" group.
    To unsubscribe from this group and stop receiving emails from it, send an
    email to [email protected].
    For more options, visit https://groups.google.com/d/optout.
    --
    You received this message because you are subscribed to the Google Groups "golang-dev" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
    For more options, visit https://groups.google.com/d/optout.
  • Jens Frederich at Dec 16, 2014 at 9:24 am ⇧
    This would work better for me too.
    On Tue, Dec 16, 2014 at 2:54 AM, Rob Pike wrote:

    This is just me speaking, not the Go team.

    I'd like to ask what people think about shifting our release cycle to
    spring and autumn rather than the current summer and winter cycles. The
    problem with the current cycle is that both release dates each year happen
    at inconvenient times on the calendar, with folks taking time off for
    official and unofficial holidays.

    The current releases are June and December. It might be easier if they
    happened two or three months later (although still on the 6 month cycle),
    say September and March. To do this, we'd need to have an 8 or 9 month
    cycle first, but the 1.5 release is a major upheaval so it seems like a
    good candidate for having a little extra time to get the bugs out.

    Please let me know what you think. Again, this is not an official
    proposal, just a question for now.

    -rob

    --
    You received this message because you are subscribed to the Google Groups
    "golang-dev" group.
    To unsubscribe from this group and stop receiving emails from it, send an
    email to [email protected].
    For more options, visit https://groups.google.com/d/optout.
    --
    You received this message because you are subscribed to the Google Groups "golang-dev" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
    For more options, visit https://groups.google.com/d/optout.
  • David du Colombier at Dec 16, 2014 at 9:50 am ⇧
    I thought exactly the same. I agree with this proposal.

    --
    David du Colombier

    --
    You received this message because you are subscribed to the Google Groups "golang-dev" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
    For more options, visit https://groups.google.com/d/optout.
  • Lucio De Re at Dec 16, 2014 at 10:49 am ⇧
    For what it's worth, I also think this is a great idea.

    Of course, one only gets this one chance; going back to the previous
    cycle in future isn't really an option, is it? Just thought I'd
    mention it, I don't think the need is likely to arise and if it does,
    then one just skips one release cycle.

    Lucio.

    --
    You received this message because you are subscribed to the Google Groups "golang-dev" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
    For more options, visit https://groups.google.com/d/optout.
  • Brad Fitzpatrick at Dec 16, 2014 at 10:51 am ⇧
    Anything is an option.

    On Tue, Dec 16, 2014 at 9:49 PM, Lucio De Re wrote:

    For what it's worth, I also think this is a great idea.

    Of course, one only gets this one chance; going back to the previous
    cycle in future isn't really an option, is it? Just thought I'd
    mention it, I don't think the need is likely to arise and if it does,
    then one just skips one release cycle.

    Lucio.

    --
    You received this message because you are subscribed to the Google Groups
    "golang-dev" group.
    To unsubscribe from this group and stop receiving emails from it, send an
    email to [email protected].
    For more options, visit https://groups.google.com/d/optout.
    --
    You received this message because you are subscribed to the Google Groups "golang-dev" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
    For more options, visit https://groups.google.com/d/optout.
  • Aram Hăvărneanu at Dec 16, 2014 at 12:10 pm ⇧
    I strongly support this as well.

    --
    Aram Hăvărneanu

    --
    You received this message because you are subscribed to the Google Groups "golang-dev" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
    For more options, visit https://groups.google.com/d/optout.
  • Luna Duclos at Dec 16, 2014 at 10:26 am ⇧
    This would be a positive change for us as well
    On Tue, Dec 16, 2014 at 2:54 AM, Rob Pike wrote:

    This is just me speaking, not the Go team.

    I'd like to ask what people think about shifting our release cycle to
    spring and autumn rather than the current summer and winter cycles. The
    problem with the current cycle is that both release dates each year happen
    at inconvenient times on the calendar, with folks taking time off for
    official and unofficial holidays.

    The current releases are June and December. It might be easier if they
    happened two or three months later (although still on the 6 month cycle),
    say September and March. To do this, we'd need to have an 8 or 9 month
    cycle first, but the 1.5 release is a major upheaval so it seems like a
    good candidate for having a little extra time to get the bugs out.

    Please let me know what you think. Again, this is not an official
    proposal, just a question for now.

    -rob

    --
    You received this message because you are subscribed to the Google Groups
    "golang-dev" group.
    To unsubscribe from this group and stop receiving emails from it, send an
    email to [email protected].
    For more options, visit https://groups.google.com/d/optout.
    --
    You received this message because you are subscribed to the Google Groups "golang-dev" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
    For more options, visit https://groups.google.com/d/optout.
  • Robert Griesemer at Dec 16, 2014 at 7:17 pm ⇧
    I'm ok with this.
    - gri
    On Mon Dec 15 2014 at 5:54:54 PM Rob Pike wrote:

    This is just me speaking, not the Go team.

    I'd like to ask what people think about shifting our release cycle to
    spring and autumn rather than the current summer and winter cycles. The
    problem with the current cycle is that both release dates each year happen
    at inconvenient times on the calendar, with folks taking time off for
    official and unofficial holidays.

    The current releases are June and December. It might be easier if they
    happened two or three months later (although still on the 6 month cycle),
    say September and March. To do this, we'd need to have an 8 or 9 month
    cycle first, but the 1.5 release is a major upheaval so it seems like a
    good candidate for having a little extra time to get the bugs out.

    Please let me know what you think. Again, this is not an official
    proposal, just a question for now.

    -rob

    --
    You received this message because you are subscribed to the Google Groups
    "golang-dev" group.
    To unsubscribe from this group and stop receiving emails from it, send an
    email to [email protected].
    For more options, visit https://groups.google.com/d/optout.
    --
    You received this message because you are subscribed to the Google Groups "golang-dev" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
    For more options, visit https://groups.google.com/d/optout.
  • Russ Cox at Dec 16, 2014 at 10:09 pm ⇧
    The current cycle is:

    Dec, Jan, Feb: work
    Mar, Apr, May: freeze
    RELEASE Jun 1
    Jun, Jul, Aug: work
    Sep, Oct, Nov: freeze
    RELEASE Dec 1

    The trouble I have is that work phases get hit with both the summer and
    winter vacations, so we end up with very short amounts of time for real
    work. Shifting +3 months would move that problem completely onto the
    freezes.

    Rob and I are now thinking maybe it makes sense to shift +2 months instead
    of +3 months, so that the split is different:

    Feb, Mar, Apr: work
    May, Jun, Jul: freeze
    RELEASE Aug 1
    Aug, Sep, Oct: work
    Nov, Dec, Jan: freeze
    RELEASE Feb 1

    This shifts the vacations more into the freezes, but not completely.

    To get to that cycle from where we are now, we'd add two months to the
    current release (except one month is basically gone already), picking up
    with the freeze on May 1.

    That's the new proposal. Thoughts?

    Russ

    --
    You received this message because you are subscribed to the Google Groups "golang-dev" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
    For more options, visit https://groups.google.com/d/optout.
  • Dave Cheney at Dec 16, 2014 at 10:17 pm ⇧
    Still LGTM.

    This proposal is also fits better with the Ubuntu release cycle, so if I
    can vote twice (with different persona), LGTM.
    On 17 Dec 2014 09:09, "Russ Cox" wrote:

    The current cycle is:

    Dec, Jan, Feb: work
    Mar, Apr, May: freeze
    RELEASE Jun 1
    Jun, Jul, Aug: work
    Sep, Oct, Nov: freeze
    RELEASE Dec 1

    The trouble I have is that work phases get hit with both the summer and
    winter vacations, so we end up with very short amounts of time for real
    work. Shifting +3 months would move that problem completely onto the
    freezes.

    Rob and I are now thinking maybe it makes sense to shift +2 months instead
    of +3 months, so that the split is different:

    Feb, Mar, Apr: work
    May, Jun, Jul: freeze
    RELEASE Aug 1
    Aug, Sep, Oct: work
    Nov, Dec, Jan: freeze
    RELEASE Feb 1

    This shifts the vacations more into the freezes, but not completely.

    To get to that cycle from where we are now, we'd add two months to the
    current release (except one month is basically gone already), picking up
    with the freeze on May 1.

    That's the new proposal. Thoughts?

    Russ

    --
    You received this message because you are subscribed to the Google Groups
    "golang-dev" group.
    To unsubscribe from this group and stop receiving emails from it, send an
    email to [email protected].
    For more options, visit https://groups.google.com/d/optout.
    --
    You received this message because you are subscribed to the Google Groups "golang-dev" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
    For more options, visit https://groups.google.com/d/optout.
  • Andrew Gerrand at Dec 16, 2014 at 10:20 pm ⇧
    LGTM

    --
    You received this message because you are subscribed to the Google Groups "golang-dev" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
    For more options, visit https://groups.google.com/d/optout.
  • Jens Frederich at Dec 17, 2014 at 6:02 am ⇧
    LGTM
    On Tue, Dec 16, 2014 at 11:19 PM, Andrew Gerrand wrote:

    LGTM

    --
    You received this message because you are subscribed to the Google Groups
    "golang-dev" group.
    To unsubscribe from this group and stop receiving emails from it, send an
    email to [email protected].
    For more options, visit https://groups.google.com/d/optout.
    --
    You received this message because you are subscribed to the Google Groups "golang-dev" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
    For more options, visit https://groups.google.com/d/optout.
  • Florin Patan at Feb 9, 2015 at 10:27 am ⇧
    Hello,


    I haven't seen this answered anywhere else so I'm going to ask it here.
    Is there a concrete eta for 1.5? I'm asking this because it would be good
    for people to know when to plan various releases, especially for tools
    authors, or even conferences.
    Following the discussion, should we expect it to be in August 2015?
    Thank you.


    Kind regards,
    Florin
    On Tuesday, December 16, 2014 at 2:54:54 AM UTC+1, Rob Pike wrote:

    This is just me speaking, not the Go team.

    I'd like to ask what people think about shifting our release cycle to
    spring and autumn rather than the current summer and winter cycles. The
    problem with the current cycle is that both release dates each year happen
    at inconvenient times on the calendar, with folks taking time off for
    official and unofficial holidays.

    The current releases are June and December. It might be easier if they
    happened two or three months later (although still on the 6 month cycle),
    say September and March. To do this, we'd need to have an 8 or 9 month
    cycle first, but the 1.5 release is a major upheaval so it seems like a
    good candidate for having a little extra time to get the bugs out.

    Please let me know what you think. Again, this is not an official
    proposal, just a question for now.

    -rob
    --
    You received this message because you are subscribed to the Google Groups "golang-dev" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
    For more options, visit https://groups.google.com/d/optout.
  • Dave Cheney at Feb 9, 2015 at 10:33 am ⇧

    On Mon, Feb 9, 2015 at 9:27 PM, Florin Patan wrote:
    Hello,


    I haven't seen this answered anywhere else so I'm going to ask it here.
    Is there a concrete eta for 1.5? I'm asking this because it would be good
    for people to know when to plan various releases, especially for tools
    authors, or even conferences.
    Following the discussion, should we expect it to be in August 2015?
    Yes, the release was delayed 2 months, Go 1.5 is targeted to be
    released on August 1, 2015

    http://go-talks.appspot.com/github.com/golang/talks/2015/state-of-go.slide#9

    https://github.com/golang/go/milestones
    Thank you.


    Kind regards,
    Florin

    On Tuesday, December 16, 2014 at 2:54:54 AM UTC+1, Rob Pike wrote:

    This is just me speaking, not the Go team.

    I'd like to ask what people think about shifting our release cycle to
    spring and autumn rather than the current summer and winter cycles. The
    problem with the current cycle is that both release dates each year happen
    at inconvenient times on the calendar, with folks taking time off for
    official and unofficial holidays.

    The current releases are June and December. It might be easier if they
    happened two or three months later (although still on the 6 month cycle),
    say September and March. To do this, we'd need to have an 8 or 9 month cycle
    first, but the 1.5 release is a major upheaval so it seems like a good
    candidate for having a little extra time to get the bugs out.

    Please let me know what you think. Again, this is not an official
    proposal, just a question for now.

    -rob
    --
    You received this message because you are subscribed to the Google Groups
    "golang-dev" group.
    To unsubscribe from this group and stop receiving emails from it, send an
    email to [email protected].
    For more options, visit https://groups.google.com/d/optout.
    --
    You received this message because you are subscribed to the Google Groups "golang-dev" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
    For more options, visit https://groups.google.com/d/optout.
  • Russ Cox at Feb 9, 2015 at 9:53 pm ⇧
    Yes, the below is now the plan of record. The freeze is May 1, and the
    release is August 1.


    ---------- Forwarded message ----------
    From: Russ Cox <[email protected]>
    Date: Tue, Dec 16, 2014 at 5:09 PM
    Subject: Re: [golang-dev] Release timing
    To: Robert Griesemer <[email protected]>
    Cc: Rob Pike <[email protected]>, golang-dev <[email protected]>

    The current cycle is:

    Dec, Jan, Feb: work
    Mar, Apr, May: freeze
    RELEASE Jun 1
    Jun, Jul, Aug: work
    Sep, Oct, Nov: freeze
    RELEASE Dec 1

    The trouble I have is that work phases get hit with both the summer and
    winter vacations, so we end up with very short amounts of time for real
    work. Shifting +3 months would move that problem completely onto the
    freezes.

    Rob and I are now thinking maybe it makes sense to shift +2 months instead
    of +3 months, so that the split is different:

    Feb, Mar, Apr: work
    May, Jun, Jul: freeze
    RELEASE Aug 1
    Aug, Sep, Oct: work
    Nov, Dec, Jan: freeze
    RELEASE Feb 1

    This shifts the vacations more into the freezes, but not completely.

    To get to that cycle from where we are now, we'd add two months to the
    current release (except one month is basically gone already), picking up
    with the freeze on May 1.

    That's the new proposal. Thoughts?

    Russ

    --
    You received this message because you are subscribed to the Google Groups "golang-dev" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
    For more options, visit https://groups.google.com/d/optout.

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupgolang-dev @
categoriesgo
postedDec 16, '14 at 1:54a
activeFeb 9, '15 at 9:53p
posts17
users12
websitegolang.org

12 users in discussion

Dave Cheney: 3 posts Russ Cox: 2 posts Jens Frederich: 2 posts Andrew Gerrand: 2 posts Luna Duclos: 1 post Aram Hăvărneanu: 1 post Florin Patan: 1 post Lucio De Re: 1 post David du Colombier: 1 post Rob Pike: 1 post Brad Fitzpatrick: 1 post Robert Griesemer: 1 post

Content

People

Support

Translate

site design / logo © 2023 Grokbase