On 25.08.2012 07:58, Vincent PINON wrote: > Hi list! > Yesterday I spent some time on the bug tracker, trying to get a better > visibility by gathering related tickets, closing (apparently) solved > issues, etc.
Thanks! > I processed as I am used to do on personal/work projects, however going > a bit further in older entries I wonder if I did the job well as you > were used to do. > I am sorry if I put a mess by acting too quickly! > For example, very old entries that are handled for long are not closed > but in acknowledged state. > For me the signification of this state was "ok, I understood & > reproduced the problem, I will handle it asap", but probably I am wrong. > Is there anywhere a reference you agreed on for the use of this tool? > How do you use it? If a bug has been solved in a previous version, we close it. For current versions we set it to resolved and close all of them when we release this version (this can be done in a batch command). The remaining states are self-explanatory, I think :) Simon ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Kdenlive-devel mailing list Kdenlive-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kdenlive-devel
