Nikolai Pretzell wrote:
So I'd suggest:
- Summary looks like: Valgrind ID: ,
- The issues get the keyword "valgrind".
I think that's a good idea.
Kind regards, pl
--
If you give someone a program, you will frustrate them for a day;
if you teach them how to program, you will frustrate them f
Hi Bernd,
> Well except from that it is basically just a file and not a database
> where we keep track of what valgrind already found in previous runs and
> for which errors tasks have already been submitted you are right there
> is additional storage involved. With each valgrind run that file
Frank Schönheit - Sun Microsystems Germany wrote:
Hi Nikolai,
Hi Frank,
The Valgrind ID is indeed a needed information. It is used to identify
issues during the Valgrind run when IssueZilla ids are not yet known. It
is not needed for the developer fixing it, but helps to relate the tasks
Hi Nikolai,
> The Valgrind ID is indeed a needed information. It is used to identify
> issues during the Valgrind run when IssueZilla ids are not yet known. It
> is not needed for the developer fixing it, but helps to relate the tasks
> easily to the valgrind-result-data.
Ah, so we have some d
Hi Frank and Philipp,
if there is a keyword "valgrind", we should use this.
Nevertheless the information "Valgrind" in the summary is useful and
IMHO should stay there. Putting the error into the summary seems to me a
good idea, still the summary won't be too long.
The Valgrind ID is indeed
Hi Philipp,
> Still i want to
> be able to see from the title what an issue is generally about. A tool
> can never know that, so at least the valgrind title tells me what class
> of issues this belongs to.
Okay, that's a point.
>>Do Valgrind bugs really have an ID? (I mean, except the issue I
Frank Schönheit - Sun Microsystems Germany wrote:
Hi Philipp,
There's a keyword "valgrind"
(http://www.openoffice.org/issues/describekeywords.cgi), which already
captures this information - IMO duplicating this information in the
summary is prone to errors, and should be avoided.
Since leaving
Hi Philipp,
>>There's a keyword "valgrind"
>>(http://www.openoffice.org/issues/describekeywords.cgi), which already
>>captures this information - IMO duplicating this information in the
>>summary is prone to errors, and should be avoided.
>
> Since leaving "Valgrind" out of the summary would leav
Frank Schönheit - Sun Microsystems Germany wrote:
Hi Nikolai,
in a few weeks and beyond, there may occur a kind of IssueZilla issues
whose summary starts with "Valgrind ".
There's a keyword "valgrind"
(http://www.openoffice.org/issues/describekeywords.cgi), which already
captures this informa
Hi Nikolai,
> in a few weeks and beyond, there may occur a kind of IssueZilla issues
> whose summary starts with "Valgrind ".
There's a keyword "valgrind"
(http://www.openoffice.org/issues/describekeywords.cgi), which already
captures this information - IMO duplicating this information in the
su
Hi Developers,
in a few weeks and beyond, there may occur a kind of IssueZilla issues
whose summary starts with "Valgrind ".
Please find details about those in the OOo-Wiki:
http://wiki.services.openoffice.org/wiki/ValgrindTasks
Best regards,
Nikolai
-
11 matches
Mail list logo
