Alex, you are correct that a large number of the SonarQube issues can
be closed as "won't fix". I've opened INFRA-22130 [1] so I can get
admin access to make those changes.

Gilles, what do you picture as required in order for commons-geometry
to be released? Do you see fuzz-testing as a blocker? If so, how much
fuzz testing do you think is needed before the release?

Regards,
Matt

[1] https://issues.apache.org/jira/browse/INFRA-22130

On Wed, Jul 21, 2021 at 10:36 AM Alex Herbert <alex.d.herb...@gmail.com> wrote:
>
> On Wed, 21 Jul 2021 at 13:34, Gilles Sadowski <gillese...@gmail.com> wrote:
>
> >
> > I'm not really pushing for either of the above two.  Instead, we
> > we should try and clean up everything[1][2] before the first stable
> > release.
> >
>
> With regard to SonarCloud, Matt are you able to administer the issues on
> the commons projects?
>
> If not then you can request that your github ID be added as an
> administrator of the commons projects on sonarcloud. The ticket where I did
> this is [INFRA-19172]. I asked for RNG but I have access to all the
> projects.
>
> I have not looked at the Geometry sonar report beyond seeing that it has a
> lot of issues. I am sure that many of these can be bulk closed as won't fix.
>
> Alex
>
> [1] https://issues.apache.org/jira/browse/INFRA-19172
>
>
> >
> > Regards,
> > Gilles
> >
> > [1] https://sonarcloud.io/project/issues?id=commons-geometry
> > [2] https://lgtm.com/projects/g/apache/commons-geometry/?mode=list
> >
> > > I could try to get an RC out this weekend.
> > >
> > > Regards,
> > > Matt J
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> > For additional commands, e-mail: dev-h...@commons.apache.org
> >
> >

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Reply via email to