|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.
Personally I would fork it only when really necessary, IMHO it's better to join the forces (which is actually what you already do, if it's not only coincidence of names), maintain and develop one project over to have dozen of forks, keep and eye on them and eventually cherry-pick good and needed changes (from my experience, it's quite time consuming and late response to cherry-pick something could be an issue e.g. in case of security bugs). Let's keep this issue open for a while and see how docker-java will evolve, but for now I would keep it.