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.

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

Update composer.json #82

Closed
wants to merge 1 commit into from
Closed

Update composer.json #82

wants to merge 1 commit into from

Conversation

Majed6
Copy link

@Majed6 Majed6 commented Jan 13, 2020

Update Opentracing to the latest release

@Majed6
Copy link
Author

Majed6 commented Jan 14, 2020

Updated the docs as well.

@Majed6 Majed6 reopened this Jan 14, 2020
@jukylin
Copy link
Owner

jukylin commented Feb 22, 2020

I would like to continue supporting php5.6

@Majed6
Copy link
Author

Majed6 commented Feb 22, 2020

I appreciate that but opentracing-php has dropped support for php5.6 . I was interested in upgrading opentracing to the latest release :)

@jukylin
Copy link
Owner

jukylin commented Feb 23, 2020

In fact, I'm also confused.some people or company still using the php5.6. I don't want to abandon them.

@cawolf
Copy link
Contributor

cawolf commented Jul 2, 2020

Does that mean that you do not intent to upgrade further than opentracing/opentracing:1.0.0-beta5, as this is the last version supporting PHP 5.6? If so, we will need to choose another tracer or fork this repository and maintain that, as we want to move to a stable opentracing release.

@jukylin
Copy link
Owner

jukylin commented Jul 3, 2020

Does that mean that you do not intent to upgrade further than opentracing/opentracing:1.0.0-beta5, as this is the last version supporting PHP 5.6? If so, we will need to choose another tracer or fork this repository and maintain that, as we want to move to a stable opentracing release.

I have a plan. create new version v3.0 that support the latest opentracing/opentracing, not support php 5.6 again.
Are you interested?

@cawolf
Copy link
Contributor

cawolf commented Jul 3, 2020

Yes, I am interested in that, sounds like a good plan to me. Do you want to maintain a separate 2.x branch and maintain both versions? And do you need any help?

@jukylin
Copy link
Owner

jukylin commented Jul 6, 2020

Yes, I am interested in that, sounds like a good plan to me. Do you want to maintain a separate 2.x branch and maintain both versions? And do you need any help?

Only fix bug not add new feature. If you interested, I'm going to start in August.

@cawolf
Copy link
Contributor

cawolf commented Jul 6, 2020

I'm looking forward to it. 👍

@jukylin
Copy link
Owner

jukylin commented Aug 31, 2020

Sorry, this month is too busy.Mey be you can follow opentelemetry-php.

@cawolf
Copy link
Contributor

cawolf commented Oct 12, 2020

Sorry, this month is too busy.Mey be you can follow opentelemetry-php.

No problem. Do you still want to implement the newer version branch?

opentelemetry is currently not in a useful production state, and may be in the future. However, as it merges opentracing and opencensus, it would be beneficial if this library would implement the stable opentracing release, which we are trying to release.

@jukylin
Copy link
Owner

jukylin commented Dec 26, 2020

We are working dev_v3

@nauxliu nauxliu closed this Dec 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants