List view
- No due date•0/1 issues closed
- No due date•0/4 issues closed
- No due date•0/17 issues closed
- No due date•59/60 issues closed
- No due date•0/39 issues closed
- No due date
- No due date•296/523 issues closed
- No due date•1/2 issues closed
- No due date•184/244 issues closed
- No due date•57/79 issues closed
- No due date•2/5 issues closed
- No due date•6/10 issues closed
Pkgsite issues that we plan to get to eventually, though they are not yet associated with any release milestone.
No due date•51/113 issues closed- No due date•23/43 issues closed
Gopls issues that we plan to get to eventually, though they are not yet associated with any release milestone.
No due date•61/401 issues closed- No due date•102/213 issues closed
Issues needed for gorelease integration into go command.
No due date•10/18 issues closedIssues related to licenses on pkg.go.dev. For our license policy, see https://pkg.go.dev/license-policy.
No due date•31/31 issues closedIssues that are not planned to be fixed in any other pkgsite milestones.
No due date•318/411 issues closed- No due date•22/39 issues closed
- No due date•2537/5069 issues closed
- No due date•40/78 issues closed
Proposals that are pending (not yet accepted/rejected). See https://go.dev/s/proposal-process.
No due date•3293/4260 issues closedWe maintain Go 1.4 only for the purposes of bootstrapping. There will be no more Go 1.4 releases. We provide a source-only bootstrap download for convenience. It directly tracks the release-branch.go1.4 branch. This milestone is for marking issues whose fix should be cherry-picked to release-branch.go1.4.
No due date•7/7 issues closedIssues to be fixed in the gccgo distribution (as opposed to the main Go repos).
No due date•328/393 issues closedIssues that do not affect released Go code and binaries.
Due by December 31, 2099•8064/9867 issues closedNo plan to fix in any specific release.
Due by December 31, 2099•2784/4814 issues closed