The branch idea only works if people on other platforms and compilers actually test it. As we've shown several times now, that just doesn't happen (dbus springs to mind...)
Sent from my iPhone
On 3 Aug 2010, at 13:56, ~suv <suv-sf@...58...> wrote:
On 3/8/10 13:54, J.B.C.Engelen@...1578... wrote:
I like the code checking too! When you decide adding all the bugs (grouped or not) to our bug tracker, I think you should add a specific tag "static code analysis" or something, such that they can easily be found.
Spaces can't be used in tags with Launchpad's bug tracker -> this would add 3 separate tags which would not really help with the search and by themselves don't make much sense. Why not use 'sca' as tag or even 'coverity'?
Grouping many issues by type into one bug report may make it difficult to track what parts have been committed already - OTOH filing hundreds of new bug reports will likely overwhelm the capacity of active Inkscape developers to review & commit, and leave many open reports in the bug tracker.
What about using a branch for the changes, thus being able to test compatibility across platforms and with different compiler versions without risks, and then merge with Inkscape trunk?
~suv
The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel