Yup, it sounds like a very good idea, except we shouldn't confuse bug
tracking with release scoping. Adding SUnit tests is good way of making
something get fixed, regardless of what release the fix is ready for.

Daniel

Hannes Hirzel <hannes.hirzel.squeaklist at bluewin.ch> wrote:
> 
> Hi all
> 
> Answering the mail of Kazuhiro ABE about the 'project saving bug'
> I was asking myself: 
> 
> Wouldn't it be an idea to write SUnit tests to show which bugs we want 
> to have fixed in 3.5?
> 
> This will bring back part of the burden of bug fixing from the
> harvesters
> to the community.
> 
> The SUnit GUI as is may then be used as the bug tracking tool.
> We  just work until the tests are green.
> 
> 
> -- Hannes