In any case, whatever we call as-yet-unreleased features, my views on turning HN into a running commentary on the dev process for submitters' pet projects stand.
Moreover, as I mentioned before, the software world is full of examples of this on all scales. Windows Vista lost most of its headline features before it finally shipped, after months of building up expectations by Microsoft. No project is magically immune to this possibility.
Your claim about the certainty of shipping something because a test version was integrated into a dev build is simply wrong, and that is why I use terms like "vapourware" and why I think this sort of discussion is premature for HN.
Anyway, enough of the meta.
Firefox is an open source project. Part of our mission is to enable participation by the community, and that requires doing our work in the open and talking about it in public.
I completely respect that, and I have nothing against your philosophy whatsoever.
However, I assume that Mozilla provides those who prefer to stay up to date using the dev builds with information about significant releases via other channels. Moreover, while Firefox obviously has impressive numbers of people who do stay at the bleeding edge, is that not still only a small proportion of the total user base?
If HN winds up being that channel for every major OSS project that a few HN readers use, it will look like Slashdot a few years ago -- that is, the Slashdot that many people abandoned for a while. All I'm asking is that we leave specialised discussions about in-development features to more appropriate forums, and keep HN to mainstream announcements of wider interest (such as when an important feature actually makes it into a production build of a major product) if we're going to have feature announcements at all.
Given how often my original post has been both up- and down-voted, this seems to be a fairly polarising view, however.
Personally, this is big enough news I'm happy to see it (even in a couple different forms) on HN.