[gimp-web] content: fill some more of the GIMP 2.99.12 news item.

[Jehan <jehanp src gnome org>]

commit 3d02235759e5a1d8f8c9b3a2284ed5bf7d641253
Author: Jehan <jehan girinstud io>
Date:   Wed Aug 24 22:16:28 2022 +0200

    content: fill some more of the GIMP 2.99.12 news item.
    
    I'm done for the day, I'll continue tomorrow. Anyone, feel free to
    review, cut, add, complete, fix and whatnot!

 .../2022/2022-08_GIMP-2.99.12_Released/index.md    | 504 ++++++++++++++++++---
 1 file changed, 433 insertions(+), 71 deletions(-)
---
diff --git a/content/news/2022/2022-08_GIMP-2.99.12_Released/index.md 
b/content/news/2022/2022-08_GIMP-2.99.12_Released/index.md
index 843b0ca3..4276c751 100644
--- a/content/news/2022/2022-08_GIMP-2.99.12_Released/index.md
+++ b/content/news/2022/2022-08_GIMP-2.99.12_Released/index.md
@@ -1,5 +1,5 @@
 Title: Development version: GIMP 2.99.12 Released
-Date: 2022-08-24
+Date: 2022-08-25
 Category: News
 Authors: Wilber
 Slug: gimp-2-99-12-released
@@ -129,6 +129,8 @@ worked a bit on the release note tab to allow for "demo" items.
 
 TODO: animated image + info that more is to be done. It's still WIP.
 
+### Pinching gesture in item and gradient dockables
+
 ## CMYK
 
 This one deserved a section on its own in this news report because
@@ -176,9 +178,35 @@ TODO: JPEG, TIFF, PSD.
 
 ## Themes
 
-TODO: some screenshot of the new "Default" theme in both the light and
-dark variant. Thanks to Akkana Peck for her initial contribution of the
-light theme.
+GTK got a new CSS-like theming system in GTK+ 3, which means our 2.10
+themes were not reusable and which is why we called for theme designers
+many times because a graphics application should really have a good set
+of neutral gray themes for an interface with the less color pollution,
+as it can affect your color perception.
+
+It is only a month ago that we got a first proposal for a mid-gray
+neutral theme, though this one is still a work-in-progress. On the other
+hand, it triggered our long-term contributor, [Akkana
+Peck](https://shallowsky.com/), to propose a Light theme. With quick
+back-and-forth exchanges, this one was rapidly completed and merged into
+the source tree. Nikc helped also a lot by finding solutions to annoying
+bugs where we were stuck.
+
+In the end, we made the theme more generic, making colors into variables
+with semantic names, and reused the same style code yet different colors
+to make a dark theme.
+
+Instead of having 2 themes, we merged these into a "Default" theme with
+both a light and dark variants which will be switched depending on the
+"*Use dark theme variant if available*" checkbox.
+
+For this to work, we also made a new process for theme makers, based on
+generic GTK process, which is that your theme can contain a
+`gimp-dark.css` file (additional to the main `gimp.css`). This secondary
+file will be used instead of the first when the "*Use dark theme variant
+if available*" option is checked in Preferences.
+
+TODO: screenshots.
 
 ## File format support
 ### PSD
@@ -201,65 +229,223 @@ section too.
 
 ## Build and documentation
 
-### meson
+### meson (message to packagers)
+
+GIMP build system traditionally uses GNU autotools. An initial, yet
+incomplete, port to the newer meson system was contributed in 2017 by
+Félix Piédallu.
+
+It took a few years to complete the last customizations, tweaking meson
+scripts to be able to handle all the special cases we had in GIMP code.
+As we approached completion in this development cycle, we started to
+officially recommend meson for Windows, then macOS, and finally, early
+August, we decided to recommend meson for all platforms.
+
+This is still an evaluation phase for this build system, though now we
+are moving forward into intensive testing. **If you are a packager,
+please try to now use our meson build and report any issue to us.**
+
+Exceptionally for this version, we released 2 tarballs on our [build
+server](https://download.gimp.org/pub/gimp/v2.99/):
+`gimp-2.99.12.tar.xz` and `gimp-2.99.12-autotools.tar.bz2`. As you can
+guess, the former is the meson-generated tarball, yet we left an
+autotools-generated tarball as fallback if the meson tarball end up
+having major issues.
+
+The
+[INSTALL](https://gitlab.gnome.org/GNOME/gimp/-/blob/master/INSTALL.in)
+file was rewritten as well with meson instructions.
 
-TODO: packager information, our meson build is now recommended for intensive testing.
-For this version, we released 2 tarballs (main one is meson) and INSTALL
-file was rewritten.
+Of course, all our own packages (flatpak for Linux, installer for
+Windows and DMG for macOS) are now built with meson.
 
 ### Gettext
 
-TODO: technical debt removed!
-Big work by Niels De Graef.
+As many other projects, GIMP was using the `intltool` project to extract
+localizable strings and translate various files with `gettext`, not only
+code.
+
+Since about 2016, upstream `gettext` gained ability to extract strings
+for more types of files and formats, projects were [encouraged to move
+on](https://wiki.gnome.org/MigratingFromIntltoolToGettext) and the
+`intltool` project was progressively abandoned. But GIMP was still using
+it for various types of files (XML, desktop files, Inno Setup
+translation files and more…) so the workfield was not small.
+
+Well no more as Niels De Graef finally took care of this port and got
+rid of this technical debt! 🥳
+
+Of course, it triggered various problems, even to release day as we
+realized when testing installers that some buttons were broken (which is
+one of the reasons why this news is out 4 days after the actual source
+release) and we had to fix the strings. Hopefully this was the last
+related issue!
 
 ## Platform support
 ### Wayland
 
-TODO: check exactly, but:
-
-* we can probably talk about portal issues (X11 implementation of color
-  picking is not tried in priority even if the portals exist because of
-  broken portal on some desktops and non-color managed returned values)
-* We removed keyboard grab !530 (and more grab removal still WIP) which
-  were causing issues.
-* Some issues just disappeared by updating the dependency stack as
-  Wayland is still quite new technology with many small issues.
+Wayland issues are slowly yet surely being getting rid of. Some of the
+issues we had just disappeared with more recent versions of some Wayland
+compositors. We do hope more bugs in upstream compositors will be fixed
+eventually because some serious issues are still puzzling us (such as
+crashes of some GTK applications, GIMP included, on the `Sway` Wayland
+compositor).
+
+Some other issues have been handled in our code.
+
+One of them is that early testers may have noticed a very annoying popup
+telling you that "*gimp-2.99 wants to inhibit shortcuts*" (at least on
+`Mutter`, the Wayland compositor of GNOME).
+This got fixed by removing various keyboard grabbing code which was not
+necessary anymore with GTK+3.0.
+
+Some issues still remain, based on the early state of Wayland in
+general, in particular because it doesn't have color management. We were
+often advised to use the "portals" for various features, such as color
+picking, which unfortunately do not return us color-managed colors (as a
+side issue, some desktop — such as Cinnamon and Mate — simply are
+missing implementation for the color picking portal even though the
+portal exists, which confuses GIMP). This is a *regression* problem
+because we were getting wrong colors (slightly wrong, or even very wrong
+if you use a wide gamut display) even when one were still running on
+X11. Therefore now we will favour the X11 implementation for color
+picking when you are running on X11 and will use the portals only
+on Wayland. We may go back to portals for everyone on Linux when they
+return managed colors.
+
+Meanwhile, we are in discussions with Freedesktop portal developers to
+get a new color-picking portal API, which will eventually have to be
+implemented for the various desktops. Let's hope it happens sooner than
+later! 😅
 
 ### macOS
 
-TODO:
-
-* A lot of maintenance work done by Lukas Oberhuber. It's not always as
-  visible, but packaging work is quite thankless work so we should fix
-  this!
-* Also we should talk about the huge speed improvements which will
-  appear with GTK+ 3.24.35. We should probably also thank the GTK devs
-  (esp. John Ralls and Christian Hergert, as well as a few others who
-  intervene sporadically in bug reports) which patiently helped and made
-  a lot of iterations (through several MRs) to get it right. And
-  apparently they did as now macOS GIMP is seriously fast (according to
-  lukaso feedback, I haven't tested myself).  See gimp-macos-build!86
-  then gtk!4071, gtk!4427 and finally gtk!4728.
-  https://gitlab.gnome.org/GNOME/gtk/-/issues/3714#note_1459718
-* There is also a Cairo update/patch we included, as I was told Inkscape
-  did it and it helps for slowness (though not sure if it helps as much
-  as the GTK ones): gimp-macos-build#38
-* For M1, work is still ongoing, but we are mostly blocked by hardware
-  (cf.  Infrastructure#832).
+As usual, a lot of maintenance work was done by Lukas Oberhuber.
+Packaging work is not as visible, hence is quite often thankless, which
+should be fixed: thanks Lukas as well as every other packager!
+
+Apart from this, you may remember the slowness issues happening on newer
+macOS versions (ever since Big Sur). We had some custom patches already
+for GTK and some dirty trick in GIMP code itself since [GIMP
+2.99.10](https://www.gimp.org/news/2022/02/25/gimp-2-99-10-released/#wayland-and-macos-support).
+
+It all led to some much better improvements in GTK code which took over
+the previous patches. It took months of testing, several code proposals
+in several directions (at least 3 different merge requests, possibly
+more code was discarded) and it got to a very satisfying result as Lukas
+confirmed it is much faster now and GIMP is totally usable. Our in-GIMP
+dirty tricks could also be removed.
+For all these improvements, we want to thank in particular John Ralls
+who provided the finale fixes and Christian Hergert for his constant
+inputs. Of course, we should not forget the numerous other contributors
+who stopped by to help and give useful inputs. Hopefully GTK on macOS
+will continue to improve even more!
+
+In any case, this is great news for all other multi-platform GTK
+software, though no GTK+3 release contains these fixes yet. It will be
+available in GTK+ 3.24.35.
+
+Meanwhile we also include a patch on Cairo (again by John Ralls) for
+improved performance on macOS, though not as important as the GTK fix.
+
+In any case, a lot has happened since the days, not so long ago, when we
+were [despairing of the sad state of GIMP on
+macOS](https://www.gimp.org/news/2020/12/25/gimp-2-10-22-released-macos/#whats-going-on-with-big-sur),
+with slowness (to the point of being unusable) and interface issues. Now
+we are finally getting to a point where we can hope GIMP 3.0 will be
+great on macOS, though we are still very short on contributors for this
+OS. We welcome any developer wanting to join us!
+
+Last point for people waiting for M1 builds: some work has been done in
+this direction, but we are mostly blocked by CI hardware limitations.
+We'll keep you updated on improvements for this topic obviously.
 
 ## babl and GEGL
 
 As usual, this release is supplemented with the releases of
-[babl](https://gegl.org/babl/) 0.1.94 and [GEGL](https://gegl.org/)
-0.4.38.
+[babl](https://gegl.org/babl/) 0.1.94/0.1.96 and
+[GEGL](https://gegl.org/) 0.4.38.
+
+### babl 0.1.94/0.1.96
+
+babl 0.1.94 fixes a crash on non-aligned data for SIMD and improve vala
+compatibility of introspection info.
+
+It also brings a new command line utility for converting unique colors
+from one format and/or space to another. This is very useful to us for
+testing our color conversions and verifying that GIMP code does the
+right conversions too, which is why we wrote this tool in the context of
+the color invasion project.
+
+For instance, to convert some color from sRGB to the CIELAB color space:
+
+```sh
+$ babl -f "R'G'B' u8" -t 'CIE Lab float' 100 100 100
+Converting from "R'G'B' u8" to "CIE Lab float":
+- 42.374615
+- 0.000000
+- 0.000009
+```
+
+Usage is:
 
-TODO:
+```sh
+$ babl --help
+Usage: babl [options] [c1 ..]
+Convert color data from a specific Babl format and space to another.
 
-* check the NEWS file for both release.
-* Some demo usage of the new `babl` CLI tool are in order.
-* There might be a new babl release because the tarball is broken. If
-  not, just redirect packagers to this patch:
-  https://gitlab.gnome.org/GNOME/babl/-/commit/626a9f5044e02b0360762c1b4ad24eaf412beefc.patch
+  Options:
+     -h, --help            this help information
+
+     -f, --from            input Babl format
+
+     -t, --to              output Babl format
+
+     -i, --input-profile   input profile
+
+     -o, --output-profile  output profile
+
+     -r, --intent          rendering intent
+                           it only works with an output profile
+
+     -b, --brief           brief output
+                           it can be re-entered as input for chain conversions
+
+All parameters following -- are considered components values. This is useful to input negative components.
+
+The tool expects exactly the number of components expected by your input format.
+
+The default input and output formats are "R'G'B' float" and default space is sRGB for RGB formats, or the 
naive CMYK space for CMYK formats.
+```
+
+Of course, this tool is still meant to evolve.
+
+Note that babl 0.1.96 is functionally the same as babl 0.1.94, except
+for a fix in the build system, which was preventing to build babl from a
+tarball. Packagers in particular should therefore use the latest
+version.
+
+### GEGL 0.4.38
+
+A new denoising operation called "Denoise DCT" (`"denoise-dct"`) was
+introduced by Thomas Manni. It decomposes the input buffer to sliding
+overlapping patches, calculates the DCT denoising in each patch, and
+then aggregates the denoised patches to the output buffer averaging the
+overlapped pixels.
+
+As for existing operations, the following were improved:
+
+ - `ff-load` and `ff-save`: big cleanup API cleanup, now ffmpeg-5.0 compatible
+ - `gif-load`: updated to latest upstream libnsgif version
+ - `slic`: progress reporting and improved parameter handling.
+ - `vector-fill`: updated to latest upstream ctx version
+ - `oilify`: clamp inputs to avoid nan in output
+ - `gegl:load`: fix possible double free
+ - `rgbe-write`: plug leaks in error paths
+
+Apart bug fixes, other interesting points are that the build simplified
+using GEGL as a subproject and the continuous integration has been
+rewritten to be more reliable.
 
 ## Team news
 
@@ -282,32 +468,95 @@ For our Windows installer, additionally to packagers (Jernej Simončič)
 and developers (Jacob Boerema), we want to thank
 [Sevenix](https://www.deviantart.com/sevenics) for having always been
 on-call, testing our installers for a few releases now. Sevenix also
-helps us to administer our recent [Discord
-server](https://www.gimp.org/discuss.html#discord).
+helps us to moderate our recent [Discord discussion
+channel](https://www.gimp.org/discuss.html#discord).
 
 This is true for the Linux flatpak and the macOS DMG as well, as in
 these case, only their packagers (respectively Jehan and Lukas
 Oberhuber) have been testing them before release these days. So whatever
 is your platform of choice, please join us!
 
-So it's a good reminder that you don't need to be a developer to
-contribute back. There are tasks for packagers, testers, translators,
+It's a good reminder that you don't need to be a developer to contribute
+back. There are tasks for designers, packagers, testers, translators,
 documenters and more! 🤗
 
 ## Websites
-### gimp-help
-
-TODO: talk about the new website with daily update, though we don't need
-to go in details, as it deserves its own news which we should do soon
-(possibly with a gimp-help tagged release?).
-
-### gimp-web-devel
-
-TODO: WIP for the new developer website, with a lot of help by swift and
-patdavid. Hugo port already done in-repo. Developer documentation from
-the old (lost) wiki as well as from within GIMP repository are going to
-be progressively migrated.
-Not online yet!
+### Documentation website
+
+We regularly write about this here: the [new
+maintainer](https://www.gimp.org/news/2021/09/18/gimp-2-10-28-released/#team-news)
+of the `gimp-help` repository (our documentation), [Jacob
+Boerema(https://www.jacobboerema.nl/en/), has been improving it for over
+a year now, doing much needed maintenance, removing technical debt, and
+improving what existed. But you could not see much of it… until today!
+
+Indeed he very recently updated the [online documentation
+website](https://docs.gimp.org/). As you can see, from the landing page
+already, we finally see all languages, and each of them show their
+translation ratio now. We do hope it will trigger more people to help
+and contribute to translation! 😸
+
+A daily-update process has also been set up, so that we won't ever get
+back in this bad situation of outdated online documentation for years
+(even though some contents are already fixed in-repository).
+
+The Quick Reference PDF is now also available in every supported
+language (once again with translation completion percentage showing up).
+
+Of course, a lot of actual contents still deserve more love, either
+outdated, or information about new features may be missing. There is
+just so much that a man alone can do. Yet now the infrastructure is
+there to welcome a much faster update and feedback process, so if anyone
+wants to contribute to the documentation, you should look at the
+[repository](https://gitlab.gnome.org/Infrastructure/gimp-web) and
+propose merge requests. The contribution format is *DocBook*.
+
+For translation contributions, you should get in touch with GNOME
+translation teams as they have their own platform. More information are
+available [here](https://docs.gimp.org/help.html).
+
+A dedicated news with more details on the change might soon be
+published, possibly if we decide to make a new tagged release of the
+manual, which will mean new installers for Windows, and tarballs for
+other platforms and for packagers, containing up-to-date contents.
+
+### Development website
+
+Meanwhile our [developer website](https://developer.gimp.org/) was in an
+even more dire situation as it had not been updated for over 10 years!
+
+This is about to change as one of our goal for GIMP 3.0 is to improve
+the plug-in ecosystem, not only with an upcoming [extension
+platform](https://www.gimp.org/news/2020/11/06/gimp-2-99-2-released/#extensions),
+but also with better and more up-to-date documentation.
+
+The work on the new developer website is finally starting, thanks to the
+impulsion by Robin Swift, a new contributor, and help from Pat David
+(who is the long-time contributor who already helped by [revamping our
+website](https://www.gimp.org/news/2015/11/22/20-years-of-gimp-release-of-gimp-2816/#new-website)
+and created the [PIXLS.US community](https://pixls.us/) for FLOSS
+photography tool).
+
+We already ported the website contents, away from DocBook, to the
+[Hugo](https://gohugo.io/) platform. This should simplify contributions.
+We also cleaned most of the outdated contents and started to port some
+contents which were stored in the source repository itself, and from the
+wiki.
+
+Ah, the wiki! Some people might have noticed that it is gone now. We
+used to have the roadmap, build instructions for newcomers and more
+technical or historical stuff over there. Let's say that unfortunate
+events occured, and we lost it. 😱
+
+Fortunately all the contents could be salvaged, and we are now going to
+port what is the valuable parts into the upcoming developer website,
+nicely organized.
+After all, both the wiki and the developer website were filling a
+similar purpose (with the exception that one was mostly abandoned). So
+in the end, it's a good thing, organization wise, right? 😅).
+
+It's still very early in the migration process, so we will keep you
+up-to-date with more exciting news soon.
 
 ## Mirror news
 
@@ -343,7 +592,101 @@ Thanks!
 
 ## Release stats
 
-TODO: compile some stats.
+63 people contributed to the [main
+repository](https://gitlab.gnome.org/GNOME/gimp/) for GIMP 2.99.12:
+
+* 23 developers contributed to `GIMP` code base for this micro version:
+    - 1 developer with more than 300 commits: Jehan.
+    - 4 developers with 10 to 50 commits: Jacob Boerema, Nikc, Loyd
+      Konneker, Niels De Graef.
+    - 18 developers with less than 10 commits: Povilas Kanapickas, Kevin
+      Cozens, Lukas Oberhuber, woob, Simon Budig, Anders Jonsson, Axel
+      Viala, Ben Rogalski, Claude Paroz, Daniel Novomeský, GokhanKabar,
+      Jan Tojnar, L amander, azetoy, houda, Øyvind Kolås, ktoyle and
+      Sonia Habtiche.
+* 25 translations were updated: Basque, Brazilian Portuguese, Bulgarian,
+  Catalan, Chinese (China), Danish, Dutch, Finnish, French, Galician,
+  Georgian, German, Greek, Hungarian, Icelandic, Korean, Persian,
+  Polish, Portuguese, Russian, Slovenian, Spanish, Swedish, Turkish,
+  Ukrainian.
+* 35 translators contributed: Yuri Chornoivan, Hugo Carvalho, Martin,
+  Rodrigo Lledó, Zurab Kargareteli, Luming Zh, Anders Jonsson, Fran
+  Dieguez, Sveinn í Felli, Nathan Follens, Asier Sarasua Garmendia,
+  Balázs Úr, Matej Urbančič, Alan Mortensen, Aleksandr Melman, Alexandre
+  Prokoudine, Claude Paroz, Jordi Mas, Sabri Ünal, Balázs Meskó,
+  MohammadSaleh Kamyab, Alexander Shopov, Jiri Grönroos, Piotr Drąg,
+  dimspingos, Charles Monzat, Hannie Dumoleyn, Jürgen Benvenuti, Tim
+  Sabsch, Alexandre Franke, Aryeom, Boyuan Yang, Danial Behzadi, Maíra
+  Canal and Rafael Fontenelle.
+* 4 people helped with in-code documentation: Jehan, Lloyd Konneker,
+  Niels De Graef and Akkana Peck.
+* 1 person contributed to icons: Stanislav Grinkov.
+* 3 people contributed to themes: Jehan, Akkana Peck and Nikc.
+* 13 people contributed build-related updates: Jehan, Lloyd Konneker,
+  Akkana Peck, Anders Jonsson, Jan Tojnar, L amander, ktoyle, Øyvind
+  Kolås, Lukas Oberhuber, Bartłomiej Piotrowski, Ondřej Míchal, Daniel
+  Novomeský and Jacob Boerema.
+
+These are the stats on [babl](https://gitlab.gnome.org/GNOME/babl/),
+[GEGL](https://gitlab.gnome.org/GNOME/gegl/) and
+[ctx](https://ctx.graphics/files.html) repositories:
+
+* 7 contributors to `babl` 0.1.94 and 0.1.96:
+    - 3 contributors with multiple commits: Axel Viala, Øyvind Kolås and
+      Jehan.
+    - 4 contributors with single commits: Eli Schwartz, Lukas Oberhuber,
+      Sergey Torokhov and Xavier Claessens.
+* 24 contributors to `GEGL` 0.4.36:
+    - 7 contributors with multiple commits: Øyvind Kolås, Behnam
+      Momeni, Thomas Manni, Michael Drake, Xavier Claessens, Axel Viala
+      and Anders Jonsson,
+    - 2 contributors with single commit: Felix Schwarz and Jehan.
+    - 15 translators: Hugo Carvalho, Piotr Drąg, Rodrigo Lledó, Yuri
+      Chornoivan, Anders Jonsson, Luming Zh, Martin, Zurab Kargareteli,
+      dimspingos, Alan Mortensen, Jordi Mas, Marcia van den Hout, Marco
+      Ciampa, Sabri Ünal and Tim Sabsch.
+* `ctx` doesn't have releases per-se as it is project-embedded code. So
+  let's count commits in the time frame between GIMP 2.99.10 and 2.99.12:
+    - 1 contributor with 396 commits: Øyvind Kolås.
+
+On the [documentation
+repository](https://gitlab.gnome.org/GNOME/gimp-help/), in the same time
+frame as GIMP 2.99.12, 26 people contributed:
+
+* 1 contributor with more than a hundred commits on documentation and
+  scripts: Jacob Boerema.
+* 7 contributors on the documentation itself or scripts, with less than
+  30 commits: Jehan, Anders Jonsson, Andre Klapper, Balázs Úr, Daniele
+  Forsi, Jernej Simončič and Marco Ciampa.
+* 21 translators: Rodrigo Lledó, Jordi Mas, Nathan Follens, Yuri
+  Chornoivan, Marco Ciampa, Anders Jonsson, Tim Sabsch, Hugo Carvalho,
+  Balázs Úr, dimspingos, Alan Mortensen, Aleksandr Melman, Charles
+  Monzat, Claude Paroz, Danial Behzadi, Kjartan Maraas, Luming Zh,
+  Martin, Matheus Barbosa, Milo Ivir and Ulf-D. Ehlert.
+
+On the [main website
+repository](https://gitlab.gnome.org/Infrastructure/gimp-web/):
+
+* 1 contributor contributed 76 commits: Jehan.
+* 5 contributors contributed 1 to 10 commits: Alexandre Prokoudine,
+  Anders Jonsson, Tom Gooding, Alberto Garcia Briz and Babs Keeley.
+
+On the [macOS build
+repository](https://gitlab.gnome.org/Infrastructure/gimp-macos-build):
+
+* 1 contributor contributed 71 commits: Lukas Oberhuber.
+* 1 contributor contributed 2 commits: Jehan.
+
+On the [developer website
+repository](https://gitlab.gnome.org/Infrastructure/gimp-web-devel/):
+
+* 3 contributors: Jehan, Pat David and Robin Swift.
+
+*Note: considering the number of parts in GIMP and around, and how we
+get statistics through `git` scripting and manual tweaking, errors may
+slip inside these stats. Feel free to tell us if we missed or
+mis-categorized some contributors or contributions because we try to
+acknowledge every contributor for being a part of GIMP!*
 
 ## Downloading GIMP 2.99.12
 
@@ -359,10 +702,29 @@ Other packages made by third-party are obviously expected to follow
 
 ## What's next
 
-TODO: some final text.
-
-Don't forget you can [donate to the project and personally fund several
-GIMP developers](https://www.gimp.org/donating/), as a way to give back
-and accelerate the development of GIMP. As you know, the [maintainers of
-GEGL and GIMP are crowdfunding to be able to work full-time on free
-software](https://www.gimp.org/news/2021/07/27/support-gimp-developers-sustainable-development/). 🥳
+This release is once again a major milestone towards GIMP 3.0. Every
+2.99 development versions were big milestones, but now we are really
+feeling we are getting close to release candidates with some great
+improvements happening in much needed places:
+
+* we are finally getting proper neutral-gray themes;
+* our Wayland build is finally getting a bit stabler (even though issues remain);
+* our macOS build is really on the usable side now;
+* our last remaining GTK port issues are slowly, but very surely,
+  getting taken care care of;
+* the space invasion project is showing leaps thanks to the CMYK project
+  (which forces us to review color space issues as a whole);
+* Script-fu and the API in general are getting much love;
+* several of our long-worked improvement projects are getting to an end;
+* And more as so many things are on the work!
+
+We still can't give you any date for GIMP 3.0, but we are getting there!
+🤩
+
+Don't forget you can [donate to the project and personally fund
+several GIMP developers](https://www.gimp.org/donating/), as a way to
+give back and accelerate the development of GIMP. As you know, the
+[maintainers of GEGL and GIMP are crowdfunding to be able to work
+full-time on free
+software](https://www.gimp.org/news/2021/07/27/support-gimp-developers-sustainable-development/).
+🥳