Opentelemetry-js: dev branch?

Created on 14 Jan 2020  路  5Comments  路  Source: open-telemetry/opentelemetry-js

  • [ ] This only affects the JavaScript OpenTelemetry library
  • [x] This may affect other libraries, but I would like to get opinions here first

As an end user I find myself confused about what features are available today as everything is being pushed to the master branch.

Discussion

Most helpful comment

As an end user I find myself confused about what features are available today

I think it's clear with this https://github.com/open-telemetry/opentelemetry-js/releases, WDYT ?

All 5 comments

If we want to do something like this, I would propose that we do the following:

  • dev branch takes over the role that master currently takes - the default branch that all changes are made against
  • master branch is the latest release at all times
  • continue adding x.x.x tags

As an end user I find myself confused about what features are available today

I think it's clear with this https://github.com/open-telemetry/opentelemetry-js/releases, WDYT ?

This will be heavily mitigated when we finally get gh-pages working. I'm not sure what is taking so long.

Is this still relevant?

I don't think it is!

Was this page helpful?
0 / 5 - 0 ratings