Skip to content

Compare: MinorReleases

Showing with 374 additions and 235 deletions.
  1. +5 −12 AssemblyPolicy.md
  2. +1 −1 Blogs.md
  3. +6 −0 Books.md
  4. +2 −2 CSSStyleGuide.md
  5. +15 −14 Conferences.md
  6. +1 −1 Gardening.md
  7. +1 −1 Go2ErrorHandlingFeedback.md
  8. +3 −1 Go2GenericsFeedback.md
  9. +29 −0 GoArm.md
  10. +1 −1 GoForCPPProgrammers.md
  11. +8 −1 GoGenerateTools.md
  12. +2 −0 GoUserGroups.md
  13. +32 −2 GoUsers.md
  14. +8 −1 Gomote.md
  15. +0 −1 Home.md
  16. +3 −5 IDEsAndTextEditorPlugins.md
  17. +20 −3 InstallTroubleshooting.md
  18. +3 −0 Learn.md
  19. +1 −1 MinorReleases.md
  20. +13 −3 Modules.md
  21. +2 −2 Plan9.md
  22. +168 −151 Projects.md
  23. +19 −0 ResearchPapers.md
  24. +1 −1 SQLDrivers.md
  25. +5 −5 SettingGOPATH.md
  26. +0 −1 SlowBots.md
  27. +5 −2 Spectre.md
  28. +1 −1 Style.md
  29. +2 −0 SuccessStories.md
  30. +3 −5 Ubuntu.md
  31. +1 −0 WebAssembly.asciidoc
  32. +2 −10 WhyGo.md
  33. +5 −1 golang-tools.md
  34. +6 −6 heapdump15-through-heapdump17.md
2 changes: 1 addition & 1 deletion MinorReleases.md
View file
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
Our default decision should always be to not backport, but fixes for **security issues**, **serious problems with no workaround**, and **documentation fixes** are backported to the most recent two release branches, if applicable to that branch. (for example, the most current two release branches are `release-branch.go1.13` and `release-branch.go1.14`, from which new `Go 1.13.x` and `Go 1.14.x` releases are cut) Fixes for experimental ports are generally not backported.

A “serious” problem is one that prevents a program from working at all. "Use a more recent stable version" is a valid workaround, so very few fixes will be backported to both previous issues.
A “serious” problem is one that prevents a program from working at all.

As soon as an interested party thinks an issue should be considered for backport, they open one or two “child” issues titled like `package: title [1.9 backport]`. The issue should include a link to the original issue and a short rationale about why the backport might be needed.

Expand Down