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.
Its an interesting idea, but it looks like you have a long way to go.
Brad
From: Carmine Vassallo <[email protected]>
Sent: Friday, 17 August 2018 10:41 PM
To: [email protected]
Subject: [Geotools-devel] Geotools Continuous Integration Smell Report
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 example, are you aware that you have been already working on the branch
"bradh-patch-1" for 4 weeks, while your feature branches are typically open for
3 days?
You will find this and other interesting statistics about the CI practices in
your project at
https://carminevassallo.github.io/detectorsIcons/summarizer-output/geotools_geotools/geotools_geotools.html
I would really appreciate if you could find the time to give me some feedback
on the report that I generated for you or on my tool. Please fill out the
following survey
http://www.surveygizmo.com/s3/4515476/Summarizing-the-Continuous-Integration-Process
It usually takes 7 minutes (10 minutes at maximum). As a little encouragement,
we will raffle off a 50$ Amazon voucher among all participants.
If you have questions, please replied to this email.
Thank you for your time!
Best,
Carmine.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
GeoTools-Devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
