I think we simply have not the manpower to catch up with the number of bugs reported. There are a lot of old issues that are not valid anymore or could not be reproduced anymore. But it would take a lot of time to check the status for each bug. And it would take even more time to fix the remaining ones. So I'm not sure if it would help to identify the still valid ones if we don't have the manpower to fix all of these.
At least the first part, i.e. identifying the still valid issues, could be done by some volunteers. It should not need much core knowledge to verify which issues are still valid and should be considered for a release. Ulli Am 22.10.2013 um 07:12 schrieb Andrew Gray <[email protected]>: > Hi All, > > Looking at the list of all open Bugs for the Jenkins project, (at time of > writing) there are 1,012 matching tickets. > > Many of the oldest ones like JENKINS-1640 do not appear to be active any more > despite still be open. > > Is the community ignoring these old issues since the move from Hudson to > Jenkins? > > Are all open issues still be considered active? > > I'm imagining an idealised state were we have only 100 open bugs no more than > 3 months old. > > Regards, > > Andrew > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out.
signature.asc
Description: Message signed with OpenPGP using GPGMail
