Not for the first this raises the question of who are "end users" here. I would like to believe that we try not to cater to everyone who can download firefox from Mozilla's pages. Can we expect some knowledge of what they are doing? Our software *is* server software after all.
While I agree with this statement, it might be a bit developer-centric. As a developer, you can assess the quality of a module based on these things, but it might be less obvious for normal users. After all, they are not used to seeing 'developer releases' on download pages (i.e. the mozilla download page). In fact, they might not understand the term 'developer release' to begin with. Communicating the quality and readiness of a module in simple terms is important. Communicating the quality of a module does not require us to impose rules on developers; it's mostly a UI thing and some backend work. So while I agree with what you said, keep wearing your end-user hat. :)