Go 1.2.1 will be released in early March

[Dave Cheney]

From https://groups.google.com/d/msg/golang-dev/VkSwKuEx4hY/M2FmC4xum6gJ, Go 1.2.1 will be released shortly, I heard a date of March 1, I am trying to confirm. It will contain, at this stage, these fixes

7219 database/sql: last connection in pool not handed out correctly
6987 net: ignore WSAECONNRESET AcceptEx error
6776 runtime: code text inspection confused by gdb breakpoints
6946 runtime: crash in GoroutineProfile
5139 runtime: fatal error: notewakeup - double wakeup

As this is past feature freeze, what are the options for getting these fixes into Trusty?

At this stage, with the change window on Go 1.3 closing at the end of the week, it is unlikely there will ever be a Go 1.2.2 (knock on wood).

[Robie Basak (racb)]

> As this is past feature freeze, what are the options for getting these fixes into Trusty?

Is this a bugfix-only release, or will it introduce new features?

If only bugfixes, then being beyond feature freeze is not a problem. If features, then we need a feature freeze exception from the release team.

From the upstream thread:

> (Does that mean the version of Go in 14.04 will be the same forever? If our future releases are backward compatible, can't they be included? What's the policy?)

Short answer: after release, backported high impact bugfixes only, no new features. Do upstream maintain a stable branch with a bugfix-only policy? If so, then a standing exception to stay up-to-date against that branch is possible, subject to quality requirements.

Full policy, rationale, procedure etc: https://wiki.ubuntu.com/StableReleaseUpdates

I see that 1.2.1 appears released, and from a quick look it seems that it's bugfix only. Can somebody please confirm? If this is right then we can just do it.

[Dave Cheney (dave-cheney)]

On Fri, Mar 7, 2014 at 1:49 AM, Robie Basak <email address hidden> wrote:
>> As this is past feature freeze, what are the options for getting these
> fixes into Trusty?
>
> Is this a bugfix-only release, or will it introduce new features?
>
> If only bugfixes, then being beyond feature freeze is not a problem. If
> features, then we need a feature freeze exception from the release team.

Absolutely bugfix only, and even then we didn't choose to backport
several less critical bugs.

>
> >From the upstream thread:
>
>> (Does that mean the version of Go in 14.04 will be the same forever?
> If our future releases are backward compatible, can't they be included?
> What's the policy?)
>
> Short answer: after release, backported high impact bugfixes only, no
> new features. Do upstream maintain a stable branch with a bugfix-only
> policy? If so, then a standing exception to stay up-to-date against that
> branch is possible, subject to quality requirements.

Thanks. 1.2.1 is the last of the 1.2.x series, the next version will
be 1.3 which will ship after Trusty so is not relevant.

>
> Full policy, rationale, procedure etc:
> https://wiki.ubuntu.com/StableReleaseUpdates
>
>
> I see that 1.2.1 appears released, and from a quick look it seems that it's bugfix only. Can somebody please confirm? If this is right then we can just do it.
>
> ** Tags added: upgrade-software-version
>
> ** Changed in: golang (Ubuntu)
> Status: New => Triaged
>
> ** Changed in: golang (Ubuntu)
> Importance: Undecided => Medium
>
> ** Changed in: golang (Ubuntu)
> Milestone: None => ubuntu-14.04-beta-2
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1284376
>
> Title:
> Go 1.2.1 will be released in early March
>
> Status in "golang" package in Ubuntu:
> Triaged
>
> Bug description:
> From https://groups.google.com/d/msg/golang-
> dev/VkSwKuEx4hY/M2FmC4xum6gJ, Go 1.2.1 will be released shortly, I
> heard a date of March 1, I am trying to confirm. It will contain, at
> this stage, these fixes
>
> 7219 database/sql: last connection in pool not handed out correctly
> 6987 net: ignore WSAECONNRESET AcceptEx error
> 6776 runtime: code text inspection confused by gdb breakpoints
> 6946 runtime: crash in GoroutineProfile
> 5139 runtime: fatal error: notewakeup - double wakeup
>
> As this is past feature freeze, what are the options for getting these
> fixes into Trusty?
>
> At this stage, with the change window on Go 1.3 closing at the end of
> the week, it is unlikely there will ever be a Go 1.2.2 (knock on
> wood).
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/golang/+bug/1284376/+subscriptions

[James Page (james-page)]

golang (2:1.2.1-1ubuntu1) trusty; urgency=medium

  * Merge with Debian; remaining changes:
    - 016-armhf-elf-header.patch: Use correct ELF header for armhf binaries.
    - Support co-installability with gccgo-go tool:
      - d/rules,golang-go.install: Rename bin/go -> bin/golang-go
      - d/golang-go.{postinst,prerm}: Install/remove /usr/bin/go using
        alternatives.
    - Fixes from golang trunk for better gccgo support (LP: #1271335):
      - d/p/issue27650045_40001_50001.diff:
        cmd/go: test: do not put object files where later steps will find them
      - d/p/issue28050043_60001_70001.diff:
        cmd/go: When linking with gccgo pass .a files in the order they are
        discovered
      - d/p/issue54790044_100001_110001.diff:
        cmd/go: do not require a valid archChar when using -compiler gccgo
    - d/copyright: Amendments for full compiliance with copyright format.

golang (2:1.2.1-1) unstable; urgency=low

  * New upstream release.
 -- Matthias Klose <email address hidden> Fri, 07 Mar 2014 06:03:18 +0000

[Robie Basak (racb)]

Fixed five hours by doko. Thanks!