Hi Adrian,
I think it a reasonable tradeoff at the moment. The only concern might have
been caused by licensing but is it all Apache License v2.0, so I think it is
fine.
Best Regards,
Andriy Redko
AC> Hi, team.
AC> You may be aware that we are migrating 4 repos which have some
AC> interdependence. I wanted to bring forward this concern so that it can
AC> be squashed :)
AC> While there are inter-dependencies, there's no reason why our first
AC> release should (or even can) resolve all dependencies to
AC> org.apache.zipkin.X namespaces. By releasing each repo as they are
AC> available, not as a DAG, we can move through process smoother. and in
AC> parallel. Later, we can resolve the dependencies to apache namespaces.
AC> ex. zipkin, zipkin-api, zipkin-layout and zipkin-reporter release with
AC> whatever functionality exists and on their own schedules. The next
AC> release of any of these will use whatever apache packaged dependencies
AC> are available at the time. By the time we graduate, all dependencies
AC> that are managed in apache repos will be used.
AC> Make sense?
AC> -A
AC> ---------------------------------------------------------------------
AC> To unsubscribe, e-mail: [email protected]
AC> For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
