On Thu, 08 Jan 2026 21:16, Holger Levsen <[email protected]> wrote:
hi,i'm swapping the quoted paragraphs order on purpose...On Thu, Jan 08, 2026 at 08:49:10PM +0100, Christoph Biedl wrote:For me, announcing an MBF here is an invitation to discuss. People should have a chance to raise concerns, possibly there might also be suggestions to improve the process. So at least several days between announcement and action seems very sensible. The way things were done here rather sends a message of "I'm doing things, I don't care what other people think." This is not how we should drive the project. There has already been enough stomping on my feet by developers with such an attitude.agreed!
Hi,I apologize the severity was impromptly raised just after the announcement. Note that this was not my doing; I would also like to discuss options we have first. Though I would like to point out that the severity already was at important, and that a previous MBF mail already was sent.
What I also would like to point out: GTK2 was initially released in 2002, and gtk3 has been around since 2011. That's more than 15 years. I acknowledge some widely used programs like hexchat are still using GTK2; nevertheless, I think in the long run we should get rid of it.Second, and even more confusing: The timing until actually raising thebug severity. It was less then 24 hours - while there is no reason to rush things.is there anything what Matthias/we could do now? Decrease the severity to important again? After all, its just metadata... :)
We bump ABI for libraries regularly, and the kernel API also changes.That being said I would not object if someone wants to take over the maintenance of GTK2, though I believe keeping it for beyond duke is beating a dead horse.
best, werdahias
signature.asc
Description: Digital signature
