On Sunday, August 28, 2016 06:35:38 PM Ian Clarke wrote: > I wasn't specifically thinking about moving away from Mantis, even though > nobody seems to use it any more
That is definitely not the case, it has been my primary tool for planning development for years [1]. One rule is: Before *ANY* WoT Git branch is created, it must have a bugtracker entry. The branch's name is prefixed with the bugtracker issue number. > I wonder whether the number of open bugs in our bugtracker is increasing, > staying the same, or decreasing over time? For our biggest subproject fred, it is actually decreasing for the past 180 days [2]. That's because in average our bugtracker is NOT something where users seek support - which prevents repetition of the same questions, which is nice :) It is instead mostly a place where developers document deficiencies of the codebase and potential features. There are 3300 open issues, 1000 have been filed by toad, 500 by me. So half of the bugtracker can be considered part of the codebase, which is why I'd say: We must not lose it under any circumstances whatsoever. It is our second most valuable asset besides the code itself. > What is the current process for > deciding which issue should be tackled next? - From my side: The bugtracker categories I had used and use with WoT are in a "convergent evolution" situation as compared to your task categories in the money poll, i.e. the unintentionally turned out to be very similar: * Bugs * Code quality * Features * Performance * Security * Usability For each release, I compose a draft of the roadmap on the bugtracker's roadmap page which I announce for discussion on IRC. The draft usually choses issues from each of the above categories. The goal behind that is to ensure that each release can ship a healthy mixture of all important aspects of software engineering. - keep users happy, keep developers happy, extinguish short term fires but not neglect long term quality control, etc. Given that the main goal behind my WoT work currently is to fix the performance issues, choice of individual tasks was usually easy - the ones which provide the biggest promised fix of big-O complexity were top priority. For the other categories, Mantis allows assigning a "severity" and "priority" to issues, which can be used to sort them and chose the top ones. - From the side of volunteers: Volunteers do as they please, we cannot force them to enjoy anything. So they do not seem to use the roadmap very much, but do indeed use the bugtracker to document things. Thus every few months I am eager to sit down and close a few dozens of issues which nobody else closed even though they are fixed. I'm willing to continue doing this, it's fun :) [1] https://bugs.freenetproject.org/changelog_page.php?project_id=11 https://bugs.freenetproject.org/roadmap_page.php?project_id=11 [2] https://bugs.freenetproject.org/summary_page.php (log in before clicking the link, select Project "Freenet" at top right) -- hopstolive (keyword for Ians spam filter)
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Devl mailing list [email protected] https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
