Hi hackers. Just a little reminder on the appropriate utilization of the flyspray task tracker.
- If you take over a task then please make sure to assign the task entry to you _and_ to put the task in the STARTED state. - Please remember that a NEXT task can be taken immediatly while TODO tasks are waiting for some requirement to be done. So please do not take TODO tasks. - The page http://www.gnupdf.org/Lib:Roadmap#The_Project_Plan_.28TM.29 describes the project plan and the general structure of the tasks to perform in order to complete the development of a library module. - Having two tasks A and B, A being a requirement for B, like: Foo Module unit tests design Unasigned NEXT Foo Module unit tests implementation Unasigned TODO it is ok for a developer to take both tasks: Foo Module unit tests design Mr. Foo STARTED Foo Module unit tests implementation Mr. Foo TODO Note that in this case the state of the second tasks didnt change. It is like to say: "I am working in the task A and my intention is to work in B when A is finished". - If you are working in a task A that proves to be complex enough to be splitted in several "minor" tasks then please insert the new tasks A1, A2, ..., etc. Please _dont_ remove the task A, but include a note saying that it has been splitted and introduce the right dependencies with respect A1, A2, ... Only when all the An tasks are closed then A can be closed. - Note that, in our project plan, the "Module implementation" task really means "Initial module implementation". So if a "module A implementation" task is finished and then some bug arises a new task "fix bug X in A" should be created. That's all :) PD: Gerel, I am watching you :D -- Jose E. Marchesi <[EMAIL PROTECTED]> GNU Project http://www.gnupdf.org
