RE: https://floss.social/@GIMP/116229009692048437

We released #GIMP 3.2.0 today! Quite an exhausting week with usual last-minute issues!
E.g. the CI infra suddenly failed yesterday! Fortunately admins were prompt to fix as always (still I went to bed at 1AM)!
Then issues in Windows packaging, which testers didn't notice with early test packages (of course, only noticed by someone just after the tagging! 😱).

Yet all in all, first time I end the release around 7PM after having started the release day at 9AM! The procedure gets better! 😄

@zemarmot
Yhea ! Great Job !
I seen Gimp 3.2.0 is already in Debian Testing...
Ok... tomorow : Trixie -> Forky !
Happy Gimp upgrade all !

#Gimp #Debian #Testing #Forky #tech #graphism

@brunus @zemarmot

This is the general reminder that if you are using Debian Testing, you should expect it to crash and eat all your data. The purpose of Testing is for folks to test. It is not a rolling-release.

Testing is not for production use; if your use can be described as "I need it to work", Testing is not right for that use.

@dashdsrdash @brunus @zemarmot

Stability is IMHO fine. Had a small hick up in years. More importantly: Testing gets sec updates very late. In fact Unstable first, the Stable, then maybe days later Testing.

So I run a decent Testing/Sid Frankenstein with this setup: https://github.com/khimaros/debian-hybrid

Also: just get the Gimp flatpak of this is the only more modern package u need 😉

GitHub - khimaros/debian-hybrid: run debian testing with security updates from unstable

run debian testing with security updates from unstable - khimaros/debian-hybrid

GitHub

@sihaha @dashdsrdash @zemarmot

FankenDebian is not my way.. you start with an hybrid and... finally you ends up with pure instable Sid ! 😂
And what I hate more than appimage, it's flatpak.