Bug#987659: release-notes: redmine not available, please wait backports

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

Paul Gevers wrote:
> Attached commit ready to push.

This one needs a bit of work:

> +    <section id="redmine">
> +      <!-- buster to bullseye -->
> +      <title>redmine missing in bullseye</title>
> +      <para>
> +	<systemitem role="package">redmine</systemitem> is
> +	unfortunately late migrating over to newer <systemitem
> +	role="package">rails</systemitem> version despite end of
> +	upstream support soon (currently only severe security
> +	fixes). In Debian we had to update <systemitem
> +	role="package">rails</systemitem> for other applications thus
> +	<systemitem role="package">redmine</systemitem> is not
> +	provided in bullseye. The <literal>Ruby Extras</literal>

This needs a couple of English fixes, but I think more importantly it
ought to start by stating the user-visible problem:

        The package <systemitem role="package">redmine</systemitem> is
	not provided in bullseye, as it was too late migrating over from
        the old version of <systemitem role="package">rails</systemitem>
        which is at the end of upstream support (receiving fixes for
        severe security bugs only) to the version which is in bullseye.

> +	Maintainers are following upstream closely and will be
> +	releasing a version via <ulink
> +	url="https://backports.debian.org/backports";>backports</ulink>
> +	as soon as it is released and they have working packages. Until
> +	then you may wait before upgrading, or use a VM or container
> +	running buster to isolate this specific application.
> +      </para>
> +    </section>
> +

The "You may wait before" bit doesn't work; how about:

        If you can't wait for this to happen before upgrading, you can
        use a VM or container running buster to isolate this specific
        application.
-- 
JBR	with qualifications in linguistics, experience as a Debian
	sysadmin, and probably no clue about this particular package