process for bugs and patches

Cees de Groot cg at cdegroot.com
Sun Feb 20 15:51:14 UTC 2005


On Fri, 18 Feb 2005 10:44:50 -0400, Lex Spoon <lex at cc.gatech.edu> wrote:
> Right now, on Mantis,
> everyone has to scan the whole bug log to find stuff they would know
> anything about.  I have been meaning, one day, to go searching for a bug
> tracker that can route bugs to packages, but have not had time to do so
> yet....
>
Request Tracker deals nicely with multiple queues, and it wouldn't be too  
hard to cobble something up so that people can create queues for their own  
packages. As for automatic routing, I wouldn't know how (not until the  
image really gained consciousness and can decide it by itself ;)).

Of course, I'd rather have a Squeak App for bug tracking/routing/...

> So, it seems like partitioning the image is a prerequisite to getting a
> really good process for dealing with bugs and patches.  Since
> partitioning is an advantage in other ways anyway -- reducing the code
> where we ALL have to agree on, and reducing pressure on the main patch
> harvesting process -- it seems like partitioning should be a very high
> priority.  300 klocs is daunting, and will take a while to dice into
> little pieces, but we have a good crew around here.....
>
Yup. Let's get started with it (the TFNR process, etcetera, are nice first  
small steps - nothing too risky, but nevertheless providing information  
usable by whatever package/module system we settle on).



More information about the Squeak-dev mailing list