A worthwhile reminder:
1. An absence of new releases (or even of development activity) in a software project does not in and of itself tell us anything (bad) about a project. (Common fallacy: People rushing to declare a project "dead" based on arbitrary personal expectations around commit frequency, PR turnover time and such, when they in fact don't know a thing about the project's internal processes, goals, etc.)
2. Abundant releases (or frantic development activity) in a software project does not in and of itself tell you anything (good) about a project. (Common fallacy: newer = better, more = better, bigger = better, recent = better, "better" (according to them) = better (for me))
I know this may sound a little obvious and trite, but looking at the kind of culture all around, I think it's a good idea to regularly let that sink in (I'm writing this for myself as much as for anyone reading this :)).








