Re: BUG: IR and Timers.pm

On Tue, 16 Oct 2001, Mike O'Connor wrote:

> I've log a few things via the bugs system and only got one response, now
> this may have just been a problem with every thing being so new that it got
> over looked over.
> If people thing this area is being monitored now, then I'm happy to use it.
> All thought the mail list seems to get a better response :)

:) I know. I guess the slimp3 folks are going to have to decide how to
handle it. I don't think there's anything wrong with sending everything to
the list. I'm just not sure that it's a good way of logging problems
and/or feature requests. Sourceforge could really do with a bugzilla
implementation, but until then, their issue tracker is still better than
list archives for pointing people to things that need working on.

Anyone in the admins know if you can have sourceforge email the list
anytime something important (like bug or release status) changes?

> I would like to say that I think in the case of the Development Tree it
> would be better to talk about the problem on the list, because thing move so
> fast. I would suggest that the bug list be used for release versions of
> the code.

We should talk about everything on the list. But it looks like Sean is
becomming overloaded and we've got multiple people implementing the same
features in different ways and against different versions of the code
and with varying degrees of suitability for "release".

Organizing the bug/feature list could result in visible "owners" of
different code sections. Someone (or a couple/few that are in sync) could,
for example, own the streaming stuff. He/She/They then handle merges for
streaming changes... someone else owns display features.. etc. That way
it's not a free for all, but Sean doesn't have to try to direct traffic at
6 intersections at once.

Thoughts?

--
Amos Hayes
[email protected]



To unsubscribe from this group, send an email to:
[email protected]

 

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/