You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@solr.apache.org by GitBox <gi...@apache.org> on 2022/01/12 14:01:29 UTC

[GitHub] [solr] epugh commented on pull request #515: SOLR-15910: Fork semver4j library to fix semver bugs.

epugh commented on pull request #515:
URL: https://github.com/apache/solr/pull/515#issuecomment-1011075619


   Maybe for an adjacent library, just having a fixed version that lives as someone's personal fork in Github would also be okay?  Versus bringing in this code to the Solr project itself.
   
   Github makes it too easy to get lots of forks that all end up vaguely unmaintained, and I wish it encouraged a cluster of forks like what we see for semver to somehow come back together to a single maintained approach.   Oh wait...  _community over code_ ;-)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org