"Standard" techniques to record ToDos etc? Recommendation for issue tracking

(1) Some time ago I had come across a neat technique to record todos in the
code itself that was supposedly a "standard" practice among ThoseInTheKnow.
Something like:
    self issue: #bug. "Some description"
    self issue: #todo. "Some description"

This would show up among senders of #bug #todo (somewhat to my surprise). I
can't find that web page now, anyone know the specifics? I might as well
follow the "standard".

(2) For a small team (< 4 people) developing using Squeak + Monticello, and
a small future customer base optimistically speaking (currently 0), any
recommendations on an issue tracking system? Something that understood
Monticello would be a killer ... but I won't hold my breath for that one.

Thanks - Sophie

On Jan 11, 2008 7:14 PM, itsme213 <[hidden email]> wrote:

> (1) Some time ago I had come across a neat technique to record todos in the
> code itself that was supposedly a "standard" practice among ThoseInTheKnow.
> Something like:
>     self issue: #bug. "Some description"
>     self issue: #todo. "Some description"

You're looking for #flag:. See the comment in the source of ProtoObject>>flag:.

> This would show up among senders of #bug #todo (somewhat to my surprise).

That surprised me at first, too, but it's because a method that is
called "indirectly" via #perform: needs to be found whenever you're
looking for senders.

Hope this helps!

--Tom Phoenix

itsme213 wrote:
> (1) Some time ago I had come across a neat technique to record todos in the
> code itself that was supposedly a "standard" practice among ThoseInTheKnow.
> Something like:
>     self issue: #bug. "Some description"
>     self issue: #todo. "Some description"
>
>  
self flag: #todo

should do the trick
 
Keith

Tom Phoenix schrieb: Actually, the reason might be more mundane: when looking for senders of
a given symbol, Squeak walks through each method's literals and does not
check whether the literals are actually used in message sends.
Nevertheless, this behavios is helpful.

Cheers,
Hans-Martin

Hello Sophie,

i> (2) For a small team (< 4 people) developing using Squeak + Monticello, and
i> a small future customer base optimistically speaking (currently 0), any
i> recommendations on an issue tracking system? Something that understood
i> Monticello would be a killer ... but I won't hold my breath for that one.

for sure you are aware that Squeak itself uses Mantis but there is an
issue tracker in Squeak named Gjallar. It has the ability of issues
being raised by mail, is highly configurable and well ... is written
in Squeak.

www.gjallar.se is English and Göran Krampe is the head of the bunch.
Discussions are (currently sleeping) on setools list and IRC gjallar.

If you go for it I'm curious about your experience!


Cheers

Herbert                            mailto:[hidden email]