> OK, my opinion would be to put a copy of the currently known bugs with the RC
> source. To give people a local (ie offline) list to look at. Then, why not
> use a ranking scheme, people rate how much they feel a specific bug needs
> fixing before the new version.. ie
Having people vote or rate stuff isn't likely to be useful. The signal to
noise ratio of public votes like that is bad. For example, if Chuck says
there is a serious bug in the IMAP library (like he did) then I don't care
if 500 people rate that issue as insignificant. I'd trust his opinion.
> As a major version say v5 would have lots of new features, but 4.0.6 for
> example mainly bug killings with maybe some feature improvements, 4.1 would
> contain bug killings (of course) but some new features but nothing earth
> shattering, and the bugs should be treated the same way.
For us, major revisions (V5) are for entire rewrites. V 4.1 would be for
significant new functionality and the dot-releases are for bug fixes and
moderate functionality increases. I don't think there is any need to
change that.
-Rasmus
--
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
