On 3/19/06, Sivan Green <[EMAIL PROTECTED]> wrote: > On Wed, 2006-01-18 at 15:10 +0000, Ian Jackson wrote: > > > What is a `task' ? Why the multiplication of apparently unnecessary > > concepts ? When I file a bug in the Debian BTS I do not see myself as > > `creating' a `task'. > > Yes, I realize this is very old. However, as I myself wondered about > this concept, and according to my thread list this hasn't been anwered > (I apologize in advance if this comes in error) really, how is the task > descriptor explained? Where did it originate from? (took me a while to > get used to this one)
Malone tends not to use this word in the UI anymore, mainly because over-emphasis of this as a separate concept has shown itself to be more confusing than enlightening. (jblack just the other day also asked me to explain to him what "task" meant.) In the underlying model, "bug" refers to the basic information about a problem reported in some software, e.g., the title and description of the problem. A "task" is the thing we use to track the status, assignee, priority, etc. for fixing the bug in a specific package or upstream. For example, <https://launchpad.net/products/launchpad/+bug/1000> has two tasks, each marked Rejected. <https://launchpad.net/products/gnome-panel/+bug/29192> has one task, marked Fix Released. Instead of thinking "task", it's probably easier to think of "bug #29192 in upstream gnome-panel". Cheers, -- Brad Bollenbach -- launchpad-users mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/launchpad-users
