Adding or changing the license to AfferoGPL as requested by this tracker is not a issue here, I guess. (I'm also not a lawyer.)
The tracker/discussion Raphaël is referring to is about allowing non xGPLx modules linking statically to xGPLx modules, thus the "Other proprietary" licenses that are mentioned into the check.
For me it's clear that both trackers should be combined to one solution when changing code, resulting in only one clear code change that should be communicated very well to all users before upgrading to the latest version!
Adding or changing the license to AfferoGPL as requested by this tracker is not a issue here, I guess. (I'm also not a lawyer.)
The tracker/discussion Raphaël is referring to is about allowing non xGPLx modules linking statically to xGPLx modules, thus the "Other proprietary" licenses that are mentioned into the check.
For me it's clear that both trackers should be combined to one solution when changing code, resulting in only one clear code change that should be communicated very well to all users before upgrading to the latest version!