We commonly advise not to do automatic importing of issues. Too much churn.
Issue notification email is only net-new issues from analysis to analysis. No
news is good news.
Analysis 'more often' is better. Some users analyze on each commit, some
analyze nightly, some weekly. Release to releas
dtpoi...@gmail.com said:
> I am starting up a NTPsec instance of the suite of Synopsys development
> testing tools - Coverity, Defensics and Protecode.
Thanks.
...
> Is there any interest in this level of integration and reporting?
I think we should fix any problems. I don't think we should c
I am starting up a NTPsec instance of the suite of Synopsys development testing
tools - Coverity, Defensics and Protecode.
One feature of the static analysis tool is the assignment of issue by user name
associated with the line of code in the source code management tool.
Triaged issues can be
...answers a lot of questions before they are even asked!
Compiling the git SHA string into the code (-v) is huge too.
I use that in my code and find it reliable and highly useful.
- dan
-Original Message-
From: devel [mailto:devel-boun...@ntpsec.org] On Behalf Of Hal Murray
Sent: Wed
dtpoi...@gmail.com said:
> Folks also use odd numbers for development branches and adding a dot release
> for new features.
I think we should seriously consider the odd-even aproach. That solves most
of the ambiguity problem. It uses the bottom bit of a numeric slot to
indicate firm vs fuzz
