tx I checked the inria task is too complex (the idea is to manage dependency and produce gantt about tasks). Stef
In Moose we use mainly: Type-Engineering = (Re)engineering the code base to enhance its quality Type-Defect = Report of a software defect Type-Enhancement = Request for enhancement
and from time to time: Type-Project = Long-term project or autonomous task Type-Review = Request for a code review Type-Other = Some other kind of issue
Cheers, Doru
On 7 Apr 2010, at 16:30, Stéphane Ducasse wrote:
I propose that we use
Type-Task or Type-ToDo for the management of some items that are not directly bug. Marcus? adrian? is it ok for you?
As a frist step good. I personally would like to destinguish bugs from feature requests. Bugs are bad and I want as little as possible. Feature request are good and I want as many as possible...
Another aspect is: Bugs I feel kind of responsible to fix. Feature request I say: If this is really important, someone will do it. (someone not me).
Ok I like this distinction. I will recategorise. I added some TODO items (like going to the prefecture)
Stef
Marcus
-- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- www.tudorgirba.com
"Sometimes the best solution is not the best solution."
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project