On Nov 22, 2008, at 11:38 AM, Norbert Hartl wrote:

For me the only obvious types are

Type-Defect       - Bug, soon to be fixed
Type-Enhancement  - Nice to have, not decided if and when to include

I'm not clear about these:

Type-Patch

I thought is was a fix.

Type-Mantis
something to harvest from mantis

Type-Squeak

I created them but I'm not sure if it is a good idea to have
the source of the patch inside the type. I started to add for
every mantis issue (Mxxxx) at the end of the Ticket subject. This
way it is easier to track what changes are included. And maybe this
makes Type-Mantis obsolete. What do you think?

Type-Task
Type-ToDo

are the same thing for me. And I don't like todo because it is
used for everything. I would keep Type-Task.

Fpr me todo is an invitation for other programmers to help fixing a larger
task than just a fix. This is Request for Enhancement.

Type-Other

I removed it.
I rephrase the type. Can you check?


is evil to me. It does not serve any purpose other to collect cruft.

Type-NextMilestone

I would like to see that google code offers something better than
this. The next milestone is ambiguous and you have to touch every
ticket once the next milestone is reached. I fine with it but I'm
not sure those actions are taken seriously. I'll have a look at that.

Yes I try to see but I could not find anything.


First thoughts,

Norbert
        Type-Defect = Report of a software defect
        Type-Enhancement = Request for enhancement
        Type-Task = Work item that doesn't change the code or docs
        Type-Patch = Source code patch for review
        Type-Mantis = Ticket on bugs.squeak.org to integrate
        Type-Squeak = Squeak version to integrate
        Type-Other = Some other kind of issue
        Type-ToDo = To list some todo for the coming versions
        Type-NextMilestone = To remember some actions for the next


On Fri, 2008-11-21 at 12:47 +0100, Stéphane Ducasse wrote:
Yes please suggest what we can do

Tasks -Work item that doesn't change the code or docs
Todo was related to code
and I would remove other because looks like a trashcan

Stef

On Nov 21, 2008, at 11:14 AM, Norbert Hartl wrote:

On Thu, 2008-11-20 at 21:34 +0100, Stéphane Ducasse wrote:
Hi guys

I added two type entries

        Type-Defect = Report of a software defect
        Type-Enhancement = Request for enhancement
        Type-Task = Work item that doesn't change the code or docs
        Type-Patch = Source code patch for review
        Type-Mantis = Ticket on bugs.squeak.org to integrate
        Type-Squeak = Squeak version to integrate
        Type-Other = Some other kind of issue
        Type-ToDo = To list some todo for the coming versions
        Type-NextMilestone = To remember some actions for the next
milestones

I would like that we used them to sort well the items

What's the difference between task and todo? I find todo
always too generic. "Others" is the same for me. That places
are supposed to collect cruft :) I'm just arguing because
I'm confident that less categories is better most of the
times.

Norbert


_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project



_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project



_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Reply via email to