Hi, Jenkins uses some custom builds of external libraries, typically XStream. Today such projects are hosted on github, which would make easier to keep in sync and/or propose fixes to upstream project. But we can't reconcile existing repository with project's github.
Typical sample : https://github.com/jenkinsci/xstream/ vs https://github.com/x-stream/xstream I suggest we rename such a repo on jenkinsci organization as "-legacy", then fork the upstream project, and apply a diff to ensure we get our own changes back (or maybe try to cherry-pick patches, which would be nicer but more complex). We could then ensure PR made to jenkinsci are also proposed to upstream project and we only include fixes that are strictly related to jenkins usage, or at least changes we approved might be included in a future upstream project release wdyt ? -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANMVJznvDaPk0t%2BMTbgDmiHb34eGZUT%3DLZJVCjd2VOcEcgDsyw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
