Board Review: Management Plane Namespace Review SplitIOExperimentation about sdk HOT 12 CLOSED

Hi @hahahahahaiyiwen,
I was able to get explicit approvals from an architect from each language. The namespaces in the description of this issue are now considered approved.

from sdk.

@hahahahahaiyiwen, please remove all [ and ] from the namespaces. They were supposed to be removed when you replaced [ResourceProviderName].

from sdk.

@ArthurMa1978 , we discussed this with Split when deciding our resource provider namespace "SplitIO.Experimentation", and Split wants to present their name in namespaces as "SplitIO". To be consistent, we want to use "SplitIO" instead of "Split" in SDK namespaces as well.

from sdk.

Got it, thank you @hahahahahaiyiwen.
Then the namespace is good to me.

from sdk.

Now that Arthur has given approval, we'll move on to getting the architects approval. As I mentioned we normally show the architects the proposed namespaces then wait a week to see if any of them raise any objections For this review I'll also see if we can get specific approval from each language to possible close the review faster. At the latest the review should be concluded by EoD on 5/14 if there are no objections. Once the names are approved I'll leave another comment on the issue stating so and close it out.

from sdk.

I am not sure if the release planner will automatically pick up on the namespaces mentioned in this issue, or if the release planner will pick up on the closing of this issue as the review being completed. @ladonnaq or @maririos, would either of you know the answer to that question?

I do know that when our Mgmt Plane team looks to confirm the approval of your namespaces, they will see this issue and see that they were approved.

There was a miscommunication between the SDK management plane team and Release Planner App team. The SDKs for management plane are not generated by our management plane team until later in the SDK release milestone workflow. The Release Planner App engineering team is working on a "hot fix" to resolve. I have requested that engineering manually if needed so that you are not blocked from requesting the generation and release of the SDKs by the monthly 2nd Friday cutoff (tomorrow).

from sdk.

@hahahahahaiyiwen - We were able to generate the SDKs for you so that the namespace will show-up in the drop-down box for you. You should be unblocked and able to request SDKs before the monthly 2nd Friday cutoff. If you need help you can post questions to the Azure SDK Onboarding Teams channel - https://aka.ms/azsdk/onboarding-channel.

from sdk.

@ronniegeraghty updated.

from sdk.

@ronniegeraghty The API spec PR is completed and now available in public repo https://github.com/Azure/azure-rest-api-specs/blob/main/specification/splitio/resource-manager/SplitIO.Experimentation/preview/2024-03-01-preview/splitio.json.

Is there any other open items that requires actions on our side?

from sdk.

Hey @hahahahahaiyiwen, one question: why retain the ‘IO’ suffix as the company’s name is ‘Split’ and ‘IO’ merely represents the domain?

from sdk.

Will the namespace now show in the Azure SDK Release Planner? @ronniegeraghty

from sdk.

I am not sure if the release planner will automatically pick up on the namespaces mentioned in this issue, or if the release planner will pick up on the closing of this issue as the review being completed. @ladonnaq or @maririos, would either of you know the answer to that question?

I do know that when our Mgmt Plane team looks to confirm the approval of your namespaces, they will see this issue and see that they were approved.

from sdk.