One more project lost for us thanks to gradle :(
There's no doubt, the adoption of Gradle has slowed down updates until the packaging is complete. But, software is going to change, that's just the nature of it. Nothing has been lost, we just have to rise together to the new challenge. We could have said the same thing about Maven builds before you all did the innovative work of integrating that into rpmbuild.
It's becoming very clear to me, though, that we need to get more information out there (this list is as good as any) on the status of the Gradle packaging. That will help everyone set schedules and expectations better. Let's frame it as a challenge, not a problem.