> We should wait for some positive feedback from the code being
> exercised by that new tool.  [I've no idea of how long is long enough.]

If I'm reading this link [1] correctly, it sounds like a few days
should be sufficient. (The fuzzers were merged in today.)

> Then, as a matter of preference, I'd still suggest that "Commons RNG"
> be released first (if the latter's next release is pending).

Ok. Any thoughts on a timeline for that?

Regards,
Matt J

[1] 
https://google.github.io/oss-fuzz/faq/#what-if-my-fuzzer-does-not-find-anything
On Sun, Aug 1, 2021 at 12:36 PM Alex Herbert <alex.d.herb...@gmail.com> wrote:
>
> On Sun, 1 Aug 2021 at 16:25, Gilles Sadowski <gillese...@gmail.com> wrote:
>
> > Hi.
> >
> > Le dim. 1 août 2021 à 02:57, Matt Juntunen <matt.a.juntu...@gmail.com> a
> > écrit :
> > >
> > > Hello,
> > >
> > > I've addressed a few issues since I last proposed the commons-geometry
> > > 1.0 release, namely
> > > - reducing the code smells in SonarCloud from 100+ to 8 (mostly by
> > > clearing false positives) and
> > > - removing use of checked exceptions in the IO modules (GEOMETRY-138).
> >
> > Thanks! :-)
> >
> > > I've also run fuzz testing locally on the IO modules and am pursuing
> > > integrating the project into OSS-Fuzz. So, how are we feeling about a
> > > 1.0 release?
> >
> > We should wait for some positive feedback from the code being
> > exercised by that new tool.  [I've no idea of how long is long enough.]
> >
> > Then, as a matter of preference, I'd still suggest that "Commons RNG"
> > be released first (if the latter's next release is pending).
> >
>
> I think that RNG can be released as there is nothing pending to add. I've
> updated the user guide with the latest performance tests and new API
> additions. I have not yet checked the new API to make sure all is OK with
> the new method signatures and class names.
>
> Alex

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

Reply via email to