Closed Timple closed 2 months ago
@Timple given that this package is hosted by nobleo, does it need its own release separate release team at this time? We can always split it out later if you add other maintainers.
I'm also holding off due to https://github.com/nobleo/azure-iot-sdk-c-release/pull/1
Doesn't need a release team. But is seemed to be a mandatory question
Doesn't need a release team. But is seemed to be a mandatory question
Thanks for explaining and my apologies for the confusion. The intent of the template was to request the name of an existing release team the repository should be added to, the nobleo
team makes sense to me so I'll open the PR with that.
If you have a suggested rewording for the template that makes that clearer to you. Please feel free to open a PR proposing it.
In the meantime, https://github.com/ros2-gbp/ros2-gbp-github-org/pull/491 is open to provide the release repository with its conventional name: azure_iot_sdk_c-release
. Please let me know if that works for you by approving that PR.
Ah, I didn't get that part. Might be me, I'll think of a rephrase :slightly_smiling_face:
I've modified the team name, this should still be open to create the repository.
This is now closed, but the repository https://github.com/ros2-gbp/azure-iot-sdk-c-release.git hasn't been created yet. I thought that was the idea here.
How can I get that done? I'm not allowed to create it myself it seems.
Sorry for the confusion. I neglected to deploy the changes after merging this batch of PRs. This change is now deployed and the release repository has been created using the underscored variation of the name (matching the ROS 2 package name): https://github.com/ros2-gbp/azure_iot_sdk_c-release.git
Name of the release team:
azure-iot-sdk-c-releasers? Or whatever is common:slightly_smiling_face:nobleo_team
Release repositories to add: