Re: Using JIRA instead STATUS.txt

2010-03-15 Thread Mladen Turk
On 03/15/2010 02:18 PM, Tim Funk wrote: -0.5 It might seem moving to JIRA from Bugzilla would be a better first step. Then if commit messages follow a naming convention - the commit could automagically update the JIRA bug with the commit message. This might fix the tracking desire yet keeping th

Re: Using JIRA instead STATUS.txt

2010-03-15 Thread Tim Funk
-0.5 It might seem moving to JIRA from Bugzilla would be a better first step. Then if commit messages follow a naming convention - the commit could automagically update the JIRA bug with the commit message. This might fix the tracking desire yet keeping the simplicity of the STATUS file. But

Re: Using JIRA instead STATUS.txt

2010-03-15 Thread Henri Gomez
Le 14 mars 2010 à 21:39, Mladen Turk a écrit : On 03/14/2010 07:31 PM, Konstantin Kolinko wrote: I am -1. IMHO JIRA can do a better job then status file. The questions you've raised actually show how hard it is to get something out of status. It's a mixture of hundreds of commit messages,

Re: Using JIRA instead STATUS.txt

2010-03-15 Thread Henri Gomez
-1 Status file is easily available. Le 14 mars 2010 à 21:39, Mladen Turk a écrit : On 03/14/2010 07:31 PM, Konstantin Kolinko wrote: I am -1. IMHO JIRA can do a better job then status file. The questions you've raised actually show how hard it is to get something out of status. It's a mi

Re: Using JIRA instead STATUS.txt

2010-03-14 Thread Mladen Turk
On 03/14/2010 07:31 PM, Konstantin Kolinko wrote: I am -1. IMHO JIRA can do a better job then status file. The questions you've raised actually show how hard it is to get something out of status. It's a mixture of hundreds of commit messages, references to other commit messages, p.a.o files th

Re: Using JIRA instead STATUS.txt

2010-03-14 Thread Konstantin Kolinko
I am -1. 1. Voting system in a bug tracker has its purpose: prioritizing of issues. http://www.atlassian.com/software/jira/docs/v3.13.2/voterswatchers.html What you are proposing abuses that system. 2. There are all kinds of votes: +1,-1,+0,-0, with and without arbitrary comments. 3. Patches c

Re: Using JIRA instead STATUS.txt

2010-03-14 Thread Mladen Turk
On 03/14/2010 12:06 PM, Rainer Jung wrote: On 14.03.2010 08:07, Mladen Turk wrote: Hi, I would suggest that we use JIRA instead maintaining STATUS.txt files. Each branch can then be a separate component and each status vote JIRA issue classified as either bug, feature, etc... Voting is supporte

Re: Using JIRA instead STATUS.txt

2010-03-14 Thread Rainer Jung
On 14.03.2010 08:07, Mladen Turk wrote: Hi, I would suggest that we use JIRA instead maintaining STATUS.txt files. Each branch can then be a separate component and each status vote JIRA issue classified as either bug, feature, etc... Voting is supported except that one cannot vote for the create

Re: Using JIRA instead STATUS.txt

2010-03-14 Thread Mark Thomas
On 14/03/2010 07:07, Mladen Turk wrote: Hi, I would suggest that we use JIRA instead maintaining STATUS.txt files. Each branch can then be a separate component and each status vote JIRA issue classified as either bug, feature, etc... Voting is supported except that one cannot vote for the create

Re: Using JIRA instead STATUS.txt

2010-03-14 Thread Peter Roßbach
+1 Peter Am 14.03.2010 um 08:07 schrieb Mladen Turk: Hi, I would suggest that we use JIRA instead maintaining STATUS.txt files. Each branch can then be a separate component and each status vote JIRA issue classified as either bug, feature, etc... Voting is supported except that one cannot vot