I like the idea. It helps to split the long development stream into meaningful smaller stream for further process investigation. I have not included issue stream yet in Zorro. I am making development stream pluggable. A development stream can contain zero to many sub streams. Edit sub stream, cli sub stream, unit test sub stream, build sub stream, compilation sub stream are defined already. It's fairly simple to add issue sub stream. I will add it soon.
Thanks! Hongbing
At 08:19 PM 4/15/2005, Aaron Kagawa wrote:
Hongbing,
I haven't thought this all the way through yet.. So, I'm just throwing this idea out there.. Anyway, how about adding an Issue tokenizer to your system. It seems that the most strict use of an Issue system is to manage all of our development activities. Under the most strictest Issue Management model, if I'm going to start programming an improvement to my code, then I should log that in Jira and then start programming. Of course, since we don't do this in CSDL, then I'm not sure it would be that beneficial. However, I still wonder what the episodes would look like if we had a Issue Tokenizer.
thanks, aaron
