Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Consider renaming spine-stackdriver-trace #157

Open
yuri-sergiichuk opened this issue Dec 4, 2020 · 2 comments
Open

Consider renaming spine-stackdriver-trace #157

yuri-sergiichuk opened this issue Dec 4, 2020 · 2 comments
Assignees
@armiol

Comments

@yuri-sergiichuk
Copy link
Contributor

yuri-sergiichuk commented Dec 4, 2020 •
edited
Loading

The whole "Stackdriver" branding was dropped by Google in favor of "Cloud" branding. The "Stackdriver" itself is renamed to "Cloud Operations suite" while Trace is renamed to Cloud Trace.

I'd consider renaming spine-stackdriver-trace to either spine-trace or spine-cloud-trace.
@armiol
Copy link
Contributor

armiol commented Dec 4, 2020

@yuri-sergiichuk I'd rename to spine-cloud-trace. And I would do that in 1.7.

@alexander-yevsyukov
Copy link
Contributor

Let's do it in v2.0. The renaming is a breaking change. It's better not overload 1.7 with too many incompatible changes.
And let's release v2.0 sooner.

@armiol armiol self-assigned this Jun 9, 2023
@armiol armiol moved this to 📋 Backlog in v2.0 Jun 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@armiol armiol

Labels
None yet
Projects
v2.0
Status: 📋 Backlog
Milestone
No milestone
Development

No branches or pull requests
3 participants
@armiol @alexander-yevsyukov @yuri-sergiichuk