Hey Brad,
thanks a lot for your feedback.
For now, we only consider data from TravisCI and not from GitHub to build
our recommendations.
We found that release branches are the ones causing the most of the false
positives. So the public available tool will have a configuration setting
where the u
I don’t think you are dealing with the case where branch names get reused
(including automatically by github “edit in place” functionality).
You are also flagging “you don’t update your branches” for RC branches for
releases that are already done, which seems like a good thing, not a problem.
okay, in that case master is already using a stable jts release
--
Jody Garnett
On Fri, 17 Aug 2018 at 14:37, Andrea Aime
wrote:
> Please don't, not meant to be merged right now, we'll target 2.15 and, if
> the change is not too invasive, propose a backlog later
>
> Andrea
>
> Il Ven 17 Ago 201
Please don't, not meant to be merged right now, we'll target 2.15 and, if
the change is not too invasive, propose a backlog later
Andrea
Il Ven 17 Ago 2018, 21:21 Jody Garnett ha scritto:
> With this in mind I am coordinating with James to issue a JTS 1.16.0-RC
> this weekend, so that Nuno's
>
With this in mind I am coordinating with James to issue a JTS 1.16.0-RC
this weekend, so that Nuno's https://github.com/geotools/geotools/pull/2008
can be merged.
--
Jody Garnett
On Fri, 17 Aug 2018 at 10:01, Andrea Aime
wrote:
> (you can see a prime example of mail reuse above in the subject a
(you can see a prime example of mail reuse above in the subject and below
in the body... hi Torben!)
The GeoTools 20-RC / GeoWebCache 1.14-RC / GeoServer 2.14-RC release is
scheduled for Saturday, August 18th.
Me and Alessio will be starting the release on Monday (August 20), so
please have any ch
Dear Geotools developers,
I’m Carmine, a researcher at the University of Zurich and I am interested
in supporting developers working with continuous integration (CI). I
created a reporting tool that analyzes the CI logs of a project to identify
deviations from accepted CI best practices.
For exam