Update changelog and since pragmas

[Bodigrim]

We might wish to make a release before GHC 9.4 feature freeze, so bringing changelog into order.

[sjakobi]

Cheers!

I think the following changes should be included too:

• Use unsafeWithForeignPtr in Data.ByteString.Unsafe #401
• Perf: use static table for Base16 #418
• Remove misleading outdated mentions of fusion #412

This looks like a well-sized changeset already. Is there a reason why we should hold off on cutting the 0.11.2.0 release?

In particular, I think that #401 looks like an important perf fix that should be included in the upcoming GHC 9.0 and 9.2 releases. (CC @bgamari)

[Bodigrim]

@sjakobi thanks for suggestions, updated.

Is there a reason why we should hold off on cutting the 0.11.2.0 release?

Ideally I'd like to get #417 done in 0.11.2.0, time permitting. This would simplify things for utf8-backed text.

#365 is also a very desirable improvement and lingers in our pipeline for half a year, but I do not have bandwidth to review it properly. @sjakobi if you or anyone else have time to take a look, it would be much appreciated.

It's a difficult situation: on one side I do not like to tie ourselves to GHC release cycles, on the other hand if a breaking change lands into GHC before 9.4 feature freeze, we'll have to make another release of bytestring.

[sjakobi]

In general, I'm not a fan of tying (minor) releases to the completion of certain features. AFAIK (minor) releases are a fairly cheap process, so I wouldn't mind simply cutting another release once #365 or #417 are done.

#365 is also a very desirable improvement and lingers in our pipeline for half a year, but I do not have bandwidth to review it properly. @sjakobi if you or anyone else have time to take a look, it would be much appreciated.

I hadn't realized that this PR was waiting for a review! :/ I'll try to review it soon!