Tree status for the Go 1.27 release and Go 1.28 development

[Michael Pratt]

Hi Gophers,

Go 1.27 will soon be scheduled for release (🎉!) and as described on https://go.dev/s/release, it's time to plan for Go 1.28 development. Tentatively, we expect a soft reopening (for fixes only, not new features yet) next week, and a full general tree reopening shortly thereafter. Please see the tracking issue 79581 for the latest tree status.

Please use this thread to discuss your own plans for the 1.28 development cycle and to coordinate submission.

(Reminder, this thread is for things you *PLAN TO DO YOURSELF*, not things you want other people to do.)

If you plan on working on potentially risky changes, please follow our guide in the wiki.

Thanks,
Michael for the Go team

[Michael Matloob]

Hi Gophers,

The tree is now open for general development of Go 1.28. As you submit your changes, please keep an eye on the build dashboard (https://ci.chromium.org/p/golang/g/go-gotip/console or build.golang.org) and consider waiting if there's a widespread test failure.

Any CLs that land after CL 800721 ("internal/goversion: update Version to 1.28") but target go1.27.0 must be cherry-picked to release-branch.go1.27 by you. Cherry-pick CLs can be created following the same steps as usual but do not need a backport issue or approval from the release team. During this time all approvers have permissions to submit to release-branch.go1.27. Please continue to use your judgment about what should be included this late in the Go 1.27 release cycle, and include references to applicable release-blocking issues. We’ll remove this permission to submit to release-branch.go1.27 approximately a week before Go 1.27 RC 3 and the final Go 1.27.0 release.

The release freeze for Go 1.28 will begin on Tuesday, November 24, 2026 at 11:59 PM Eastern time.

Thank you, and happy development!

Michael for the Go team

--
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 golang-dev+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/golang-dev/CALoThU-5fcpGszVwWWw1FOi_usH1xYww2GJJBQfEpMJStaaMwA%40mail.gmail.com.

[Josh Bleecher Snyder]

> Please use this thread to discuss your own plans for the 1.28 development cycle and to coordinate submission.

Time permitting (hard to predict), I plan to:

- trickle in compiler correctness bug fixes and low-hanging optimizations
- add minor/incremental optimizations to regalloc and schedule
- continue removing hand-written asm by improving the pure Go
implementation and/or the compiler

I will continue my practice of having only one live outstanding CL at
a time. Sending a new CL will be gated on the previous CL being
submitted, abandoned, and/or blocked on other work.

-josh

[Michael Pratt]

I plan to address various scalability bottlenecks that pop up in the GC when running with >256 cores and continue to experiment with making Green Tea more NUMA-aware.

[Mark Freeman]

I will be implementing untyped composite literals in the compiler/tools and decoupling the compiler/tools export data formats.

[Meng Zhuo]

I'm planing landing these for riscv64 port in 1.28:

- zvk extensions

- msan  

- libfuzzer

- crypto/{sha256,sha512,aes,chacha20} implement
- some test/codegen for rva23u64

[Daniel Morsing]

I'm planning on landing some improvements in the prove pass, using eSSA/SSI techniques.