I don�t think this is a good idea... In fact each coder is always convinced that his code is beta/alpha/released... whatever other ppl would call it different (for example all ppl are using alpha/beta icq clients and that is their released product)
I personally prefere plain descriptions, meaning: how many dependencies, environment (OS, c++/vb), license, url, project time. cya, Edrin > We should probably add also another column specifying the "completeness" of > the component, either textual (alpha, beta, release candidate, reliable for > production environment), or a % value. Of course these would have to be > submitted by the author, who will take his responsibility :-) for telling > the truth!!! _______________________________________________ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
