Bug#928026: release-notes: document the state of security support for golang packages in Buster

[Justin B Rye <justin.byam.rye@gmail.com>]

Paul Gevers wrote:
> +  <section id="golang-static-linking">
> +    <title>Go based packages</title>
> +    <para>
> +      The Debian infrastructure currently doesn't properly enable rebuilding
> +      packages that statically link parts of other packages on a large
> +      scale. Until buster that hasn't been a problem in practice, but with the

(I'm adding a stretch-to-buster tag, since if this is still true for
buster-to-bullseye then it'll at least need a change from "hasn't
been" to "wasn't".)

> +      growth of the Go ecosystems it means that Go based packages won't be

That should probably be "ecosystem", singular.

> +      covered by regular security support until the infrastructure is improved
> +      to cope with these kind of packages in a maintainable manner.

"These kind of" is normal in spoken English, but formal written
English prefers either "this kind of package" or "these kinds of
packages".  Or maybe we just want:

         to deal with them maintainably.

> +    </para>
> +    <para>
> +      If updates are warranted, they can only come via regular point releases
> +      and thus may be deployed late.

To avoid implying "too late" we might phrase this as:

         If updates are warranted, they can only come via regular point releases,
         which may be slow in arriving.

-- 
JBR	with qualifications in linguistics, experience as a Debian
	sysadmin, and probably no clue about this particular package

diff --git a/en/issues.dbk b/en/issues.dbk
index af7ca5c2..6ead1ec6 100644
--- a/en/issues.dbk
+++ b/en/issues.dbk
@@ -508,18 +508,19 @@ $ sudo update-initramfs -u
   </section>
 
   <section id="golang-static-linking">
+    <!-- stretch to buster -->
     <title>Go based packages</title>
     <para>
       The Debian infrastructure currently doesn't properly enable rebuilding
       packages that statically link parts of other packages on a large
       scale. Until buster that hasn't been a problem in practice, but with the
-      growth of the Go ecosystems it means that Go based packages won't be
+      growth of the Go ecosystem it means that Go based packages won't be
       covered by regular security support until the infrastructure is improved
-      to cope with these kind of packages in a maintainable manner.
+      to deal with them maintainably.
     </para>
     <para>
-      If updates are warranted, they can only come via regular point releases
-      and thus may be deployed late.
+      If updates are warranted, they can only come via regular point releases,
+      which may be slow in arriving.
     </para>
   </section>
 </section>