[Opendnssec-develop] RE: Process for tracking bugs

[Matthijs Mekking]

Hi,

The first part lists stuff that I already (try to) do when working on a
JIRA issue. So I approve with this.

The second part is more interesting. I have a hard time to decide
whether something needs go into JIRA. For example, if there is a report
on the mailing list, should we create a JIRA issue for it? According to
your text, only if it results in code changes. I can see another option:
Always, even if the report turns out to be an error outside  OpenDNSSEC,
or a not accepted feature request. This way, we can refer to them when
similar future reports come in.

Also, I sometimes change log levels for log messages, as I feel that the
daemon is too verbose, or not verbose enough. These are code changes,
but I don't think a JIRA report is needed for them.

Best regards,
  Matthijs



On 12/04/2012 04:40 PM, Sara Dickinson wrote:
> Hi All, 
> 
> As a follow up to the team meeting yesterday I have written a first draft of a best practices process for how we should try to use JIRA/svn to track bugs:
> 
> https://wiki.opendnssec.org/display/OpenDNSSEC/Bug+tracking+process
> 
> Please review this and let me know what you think! I'll make sure to raise it in the next team meeting for discussion too. 
> 
> Thanks.
> 
> Sara.
> 
> _______________________________________________
> Opendnssec-develop mailing list
> Opendnssec-develop at lists.opendnssec.org
> https://lists.opendnssec.org/mailman/listinfo/opendnssec-develop
> 


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 553 bytes
Desc: OpenPGP digital signature
URL: <http://lists.opendnssec.org/pipermail/opendnssec-develop/attachments/20121210/8ab08990/attachment.bin>