Friendly check-in on Flower project status #1481
Description
Hello Flower maintainers 👋,
First of all, thank you for Flower — it has been a key part of the Celery ecosystem for many of us for years.
I’m opening this issue as a friendly check-in to better understand the current status and direction of the project.
A few observations that motivated this question:
- The latest stable release on PyPI and Docker Hub is now more than 2.5 years old.
- There has been ongoing discussion about compatibility and maintenance in
This project has not seen an update in 11 months. What gives? #1438 - On the Celery side, similar concerns were raised here, with a reference back to Flower:
mher/flower is no longer being maintained, can you put your weight behind a fork? celery/celery#9814 (comment) - There are PRs that seem to significantly move things forward (notably compatibility and maintenance updates), such as:
Modernize the code for Python 3.8 #1462
but they appear to be stalled or blocked for some time now.
Given how widely Flower is still used in production (often via Docker images), it would be very helpful for the community to understand:
- Is Flower still actively maintained?
- Are new releases planned?
- Are there blockers (time, governance, CI, ownership) that prevent merging existing PRs?
- Would help from the community (reviewing, co-maintaining, releasing) be welcome?
Tagging a couple of folks who have been involved in recent discussions, in case they can share context or guidance:
@auvipy @Nusnus @ulgens
This is absolutely not meant as a complaint — just an attempt to get clarity so users and contributors can make informed decisions and possibly help unblock the situation.
Thanks again for your work, and for any insight you can share.
Best regards,
Augustin