Re: [Freemind-developer] Refactoring when going to release no good idea
A premier mind-mapping software written in Java
Brought to you by:
christianfoltin,
danielpolansky
From: Dan P. <dan...@gm...> - 2007-07-07 07:07:18
|
Hello Dimitry, I do not understand what you do not understand. New features introduce new bugs. New refactoring introduces new bugs. Thus, adding new features and refactoring increase the overall number of bugs that remain to be fixed until the final release, leading to further delay. Also, both add to the overall need for discussion, for disagreement about details of the features and their final appearance. I am not going to post any patch until the final release 0.9.0 is out. The name of the game is attention and attention span of the team. Human beings have limited attention span. If the limited attention is devoted to new features and architecture, it cannot be same time be devoted to looking for bugs and to fine tuning. The cost of refactoring for other people is that (a) there are more emails to read, (b) more bugs to be investigated and reported, and (c) that the final release is delayed. A significant delay is a significant cost, unless you expect to live eternally. As regards the process that you say is lacking, immediately stopping adding new features and stopping refactoring would be a significant step to make the final release happen. A flexible process is in place and running. As soon as there is a RC1, I will start testing and reporting bugs. So far RC1 is not there, as there are still bugs you and Chris are aware of. If there were no refactoring, no tabs feature and no allegedly urgent feature that changes the colors of the selected node, beta 10 could have already been out, or perhaps even RC1. Best regards, Dan |