Yes, because right now, they are the only two left of the main developers who keep the distribution together, although I would add @linux-aarhus to that list as well, given his frequent contributions to — among other things — manjaro-mirrors.
And that is exactly the problem. And both of them do not do it fulltime. All one-man shows are doomed in the longterm. 
I wouldn’t say that. PCLinuxOS is pretty much a one-man show — or at least, on account of the development, because Tex does have plenty of beta testers, and people taking care of running the server, administrating the forum, publishing the monthly magazine, et al — and it’s still going strong.
Granted, it’s a bit of an oddball of a distribution — they’re vehemently anti-systemd, and the last time I checked their forum, they weren’t too keen on Wayland either — with lots of legacy stuff still relying on gtk2.
And then there’s Slackware. That’s pretty much all Pat Volkerding’s work as well. There are some additional package maintainers, but Pat is their “benevolent dictator for life”.
Mind you, I’m not saying that Manjaro couldn’t use more helping hands. On the contrary. But I don’t want to slip into doom-thinking either.
Indeed. After a bit of digging, I personally do not see any reason to be concerned about the Community Driven Distribution, itself.
But, instead of leaving us hanging as @philm did. Now that he has said what he said, I think some additional explanation would help clear the air.
I don’t know where you get all of those numbers. @Teo was only speculating.
The Testing branch is crucial to the stabilization phase.
Manjaro Unstable is, for all intents and purposes, the same thing as Arch Stable. And Manjaro is far from dead. We’re just a bit understaffed right now, that’s all.
Please refrain from scaring the living daylights out of the members. We’ve just had to anonymize a member who got so scared that he switched to another distribution.
Just stop it already, please! Manjaro’s not going anywhere. We’ve been here for 14 years already, and we plan on being here for a whole lot longer still.
I even made personal stickers for my team with Manjaro and kangaroo themes, don’t go anywhere.
How can i know this? He wrote that he was speculating after my message!
Im aware about this… same as EndeavourOS (beside that we still have official repository) that’s why i wrote as the last straw.
It’s not that i want to have this scenario.
Strange that you pretend now as this would be crystal clear for everyone 
If this is the case fine… so what took you so long too extinct the fire before it could spread? And why is this Topic then unlisted? So everything is fine… its not that this question was asked several times already and nobody answered yet… besides you.
But for sure, i will stop… when there is really nothing to worried about, im more than fine with that.
Not that it would matter much but I referred to the Public Broadcasting Service (sorry i wrote system) and this isn’t some private media company but rather founded as alternative to these companies somehow similar in purpose (but financed rather differently) as the ÖR in Germany or the BBC in the UK. Financing such a service via donations mostly may be somewhat surprising for Europeans - rather already the existence seems to be a surprise.
What is different from a TESTING branch update and a STABLE branch update
A stable branch update most likely also includes ISO images, at least from the main editions, shipping Plasma, GNOME and XFCE. Also more people than in other branches will use those packages. So doing a stable update is therefore more complex. Most likely install medias might be usable after one week of a stable update was done and missed issues fixed from the feedback of stable branch users.
A testing branch update most likely doesn’t always have an install media for testing. However, when there is a new major release upcoming, we may share also ISOs for those updates. When users of the testing branch report issues, those can be fixed easier, as we have a less big update gap of packages.
unstable branch users mostly report more frequent and are the brave ones knowing their system and are able to fix issues on the spot on their machines.
As a user you can use any branch and update on your own speed, as the only difference are suggested updates you can check or trust the set of available packages won’t break your system.
Manjaro update concept in a nut-shell
Manjaro is syncing packages from Arch-Stable, still manually, to get new packages into the Manjaro repos. Then a team of core package maintainers is checking if there are rebuilds needed or our own packages may need updates or code changes. When a set of packages is ready a snap to testing branch is normally done. However, since some maintainers sync multiple times a day or more often than usual it may take longer to slow down and prepare a proper package-set for testing.
When the core package maintainers think they have a good package-set normally the users of testing branch should give us feedback if we missed some issues or not. Then the core package maintainers normally should work on those issues and fix them on testing branch. However, most simply just focus on the unstable branch and only few maintainers monitor issues found on testing.
Then, when all is dandy testing ISOs should have been created and tested by the maintainers and the testing branch users. If all is fine, a snap to stable branch should happen, the missing issues fixed and the final install medias created plus properly announced.
After that the cycle should be repeated and synced from Arch-Stable again.
So in conclusion: every single person complaining that stable got not updated is actually on the wrong branch and should switch to testing: Switching Branches - Manjaro
Financial side of things
Regardless of how money comes in, the Manjaro project needs some money to exist. The base IT-infrastructure costs are around 350 to 400 EUR these days. Sure it can be optimized. Any other costs are for Manjaro members either doing stuff part-time or full-time. Additional costs may be for hardware or things like travel expenses.
If people expect things to be done faster, then more time and effort needs to be done, which may higher the costs of the project overall.
In the past most members of the Manjaro project were employed and did Manjaro as a hobby or in part-time. 2019 we had the opportunity to get some people paid to do things in full-time based on the fact that a company joined our efforts and funded those for a while. Those members of the company were/are still members of the developer community of Manjaro and tried to get some extra funding due to commercial projects into the Manjaro eco system. Members of the company changed and the remaining members mostly lived off from their personal savings the past two years.
Future of Manjaro
Well, it depends …
Because the thread is very long already, and I had overlooked part of your post. Someone reminded me of it, so I went back to read it and then replied to the paragraphs I had missed.
In addition to that, I also have other things to tend to here on the forum, and I am battling several medical conditions, of which some are quite severe.
I am sorry to hear that. Geçmiş olsun, I wish you a speedy recovery.
Im sorry to hear that, i can write a book about medical conditions too 
This doesn’t look to me, that you both on the same page.
Im never heared this negativity from Philm before 
And im just here, to give some points if there is a way to fortify the project.
Nothing wrong to fix a little problem, which might to become a bigger problem in future, right?
Meh, he’s just being moody. 
why not display message in pacman ?
use a post hook z-manjaro.hook :
if installed > 3 months and not in vm :
# and ?
echo "making a donation is ... https://..."
In pacman…will be a bit too much, sorry.
manjaro-hello has a Donate button linked to manjaro.org/donate
Update announcements also have a request for donations
Manjaro, like many other open-source projects, relies on the generosity of its community through donations and corporate sponsorships to support its growth and development. These donations are essential in covering the various expenses incurred in the operations of the project such as server costs, software development tools, infrastructure expenses, training, flying people to events or conferences and the salaries of key developers. With the help of these donations, Manjaro is able to secure the necessary financial stability that allows the project to continuously improve and remain active. If you love Manjaro, consider to donate!
Still no huge update, I think something is broken.
Possibly your expectation to stable branch 
I’m curious - what kind of bugs or broken behaviour are you experiencing when you use your Manjaro installation?