[Docs] Migrate azure-cognititiveservices-computervision from legacy pipeline to current

Azure / azure-sdk-for-java

This repository is for active development of the Azure SDK for Java. For consumers of the SDK we recommend visiting our public developer docs at https://docs.microsoft.com/java/azure/ or our versioned developer docs at https://azure.github.io/azure-sdk-for-java.

MIT License

2.34k stars 1.98k forks source link

[Docs] Migrate azure-cognititiveservices-computervision from legacy pipeline to current #27964

Closed scbedd closed 6 months ago

scbedd commented 2 years ago

This is in context of Azure/azure-docs-sdk-java.

Currently exists in main-source-based
Repo.json config
Code2yaml config

We want to migrate this package to the packages.json/maven method instead of leaving it on source-based.

We want to target version 1.0.9-beta. @samvaity confirmed that the SOURCES jar is present.

scbedd commented 2 years ago

hey @sima-zhu can you please take a look at this when you have a couple minutes?

sima-zhu commented 2 years ago

We can use source jar for computer vision. If they don't use our release pipeline, then every time they want to update the version, they have to manually submit the PR for updates. https://github.com/Azure/azure-docs-sdk-java/pull/2192

danieljurek commented 2 years ago

@sima-zhu -- We may need to do additional configuration to keep this from begin overwritten by content in main-source-based

danieljurek commented 2 years ago

I think in here -- https://github.com/Azure/azure-docs-sdk-java/blob/main/temporary-src-based-yml/migration.json#L21

sima-zhu commented 2 years ago

https://github.com/Azure/azure-docs-sdk-java/pull/2193/files

github-actions[bot] commented 6 months ago

Hi @scbedd, we deeply appreciate your input into this project. Regrettably, this issue has remained inactive for over 2 years, leading us to the decision to close it. We've implemented this policy to maintain the relevance of our issue queue and facilitate easier navigation for new contributors. If you still believe this topic requires attention, please feel free to create a new issue, referencing this one. Thank you for your understanding and ongoing support.