You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@servicecomb.apache.org by GitBox <gi...@apache.org> on 2019/01/14 02:49:28 UTC

[GitHub] zenlinTechnofreak edited a comment on issue #1057: Upgrading Zipkin 2.4.2 to Zipkin 2.11.12, should we remain the earlier version suporting?

zenlinTechnofreak edited a comment on issue #1057: Upgrading Zipkin 2.4.2 to Zipkin 2.11.12, should we remain the earlier version suporting?
URL: https://github.com/apache/servicecomb-java-chassis/issues/1057#issuecomment-453890285
 
 
   @liubao68 
   What I concern about is that we should keep ServiceComb compatible with the latest version of the surrounding ecosystem. Software in the ecosystem will often release new versions,  if we remain the elder code each time, we will grow strange, In that way,Java-Chassis will have code with Zipkin 2.11.12, Zipkin 2.4.2, and Zipkin 3.x.x in the near future.
   
   Therefore, what about just keep it compatible with the latest version of the software in the surrounding ecosystem?

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services