In message <20220701064342.5gxgebwj2mq5ksh6@runtux.com>,
Ralf Schlatterbeck writes:
>Ralf Schlatterbeck added the comment:
>
>On Thu, Jun 30, 2022 at 11:53:23PM +0000, John Rouillard wrote:
>> 
>> Marcus, have you tested my latest patch and verified that it works for you
>> if you set the feature flag as documented in doc/upgrading.txt?
>
>He's on vacation, I'll look into your patch and test it here.
>Note that I think that the feature flag default should be *on*
>eventually:

If it still oooks fine by the time 2.3.0 is released, the feature flag
will become a no-op and only the patched version will be present. I
only threw the feature flag in because it came in at the last minute
and I wanted to make it available for testing.

>We may want to set it to *off* now and warn users in the
>release note that they should test it with the feature turned on because
>it will change in the next release? What do you think?

That's my intent for the 2.3.0 release. The docs include the following
lines (the patch attached tothe issue has a typo 2.0.2 in place of
2.2.0) :

  Note that this is experimental and was added
  during the 2.2.0 beta period, so it is hidden behind a feature flag.
  If you use this and it works better for you please followup with an
  email on the roundup-users at lists.sourceforge.net.

Thanks.