[Geany-devel] Ideas on increasing quality of plugins

Enrico Tröger enrico.troeger at xxxxx
Wed Mar 9 19:07:45 UTC 2011

On Wed, 9 Mar 2011 14:51:36 +1100, Lex wrote:

>On 9 March 2011 09:11, Matthew Brush <matthewbrush at gmail.com> wrote:
>> On 03/08/11 10:58, Enrico Tröger wrote:
>>> As I'm currently reworking the system to create the nightly builds,
>>> we could integrate such checks into the nightly builds, maybe run
>>> cppcheck on the sources after the builds and present the results
>>> somewhere on nightly.geany.org.
>> A couple ideas:
>> 1) Parse cppcheck XML output with Python[1] (or whatever) and remove
>> any failing plugins from the main Makefile.am listed in the
>> 'plugins' variable so they don't build.
>Disagree with removing plugins from nightly builds, testing will find
>many more errors than these checks will, and removing the plugin makes
>it unavailable for testing.  I would support having failing plugins as
>a second tier release, but never remove access completely.


>> 2) Use the HTML report[1] script (uses awesome Pygments) for
>> displaying results as you mentioned.

Sounds interesting. Will have a look at these after I finished
reworking the nightly build setup. Though this might take another two
or three weeks.


Get my GPG key from http://www.uvena.de/pub.asc
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.geany.org/pipermail/devel/attachments/20110309/edb8be4c/attachment.pgp>

More information about the Devel mailing list