I wonder if there's a sane way to plan in quarterly or twice-a-year
quick checks for these issues. That'd let us address the issues without
needing it to be someone's daily struggle.
Thoughts about an (optional) routine like that being 'added' to the
six-month release cycle?
Cheers,
Jim
On 4/21/2020 12:33 PM, Andrea Aime wrote:
On Tue, Apr 21, 2020 at 6:21 PM Mark Prins <mc.pr...@gmail.com
<mailto:mc.pr...@gmail.com>> wrote:
I know some people are not too keen on these kind of notifications
/ noise.
He he... to draw a parallel, let's have a look at the QA checks.
QA stuff could be added in the PR machinery, so that if one breaks it,
they have to fix it before merging. Makes it easy and predictable,
identifies who
has to work on it automatically.
Security advisories pop up any time, there is no one on the line to
fix them,
and for a bunch of dependencies we have, fixes are a far cry away from
just
changing a pom file. You had an easy run with the Oracle driver upgrade,
others are much more painful (international code sprint grade).
It's true that sometimes it's just a matter of updating a dependency,
or marking
a false positive in the build.
So my observation is, we cannot find the time to look at the build
right now, and
do the easy ones... and the build stays on red. Say someone makes an
extra effort*
to care for the easy ones, and keep the build on green for a bit.
The first hard one to fix one is gonna peg the build on red... and we
are back to square one.
Long story short, the issue IMHO is not having the build, it's finding the
manpower to go after the reports.
Cheers
Andrea
*: hint, not me
== GeoServer Professional Services from the experts! Visit
http://goo.gl/it488V for more information. == Ing. Andrea Aime
@geowolf Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A
55054 Massarosa (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob:
+39 339 8844549 http://www.geo-solutions.it
http://twitter.com/geosolutions_it
------------------------------------------------------- /Con
riferimento alla normativa sul trattamento dei dati personali (Reg. UE
2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
precisa che ogni circostanza inerente alla presente email (il suo
contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
operazione è illecita. Le sarei comunque grato se potesse darmene
notizia. This email is intended only for the person or entity to which
it is addressed and may contain information that is privileged,
confidential or otherwise protected from disclosure. We remind that -
as provided by European Regulation 2016/679 “GDPR” - copying,
dissemination or use of this e-mail or the information herein by
anyone other than the intended recipient is prohibited. If you have
received this email by mistake, please notify us immediately by
telephone or e-mail./
_______________________________________________
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel
_______________________________________________
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel
