search

Azure / azure-sdk-tools

Tools repository leveraged by the Azure SDK team.
MIT License
110 stars 172 forks source link

Release Plans that need status changed to "Abandoned" or "Complete" #8290

Closed ladonnaq closed 2 days ago

ladonnaq commented 3 months ago

The Onboarding PM team is following up with service partners who have overdue release plans.

The following release plans need state changed to "Abandoned".

The following release plans need state changed to "Complete".

Table of release plan IDs and the new state. I tagged the release plan work items with the appropriate tag and exported query to create a table so it would be easier for me to track. I used the tags auto-complete and auto-automate.

Status ReleasePlanID Tags
✅ 1360 auto-abandon
✅ 1350 auto-abandon
✅ 1339 auto-abandon
✅ 1331 auto-abandon
✅ 1328 auto-abandon
✅ 1316 auto-abandon
✅ 1310 auto-abandon
✅ 1294 auto-abandon
✅ 1288 auto-abandon
✅ 1279 auto-abandon
✅ 1272 auto-abandon
✅ 1271 auto-abandon
✅ 1266 auto-abandon
✅ 1263 auto-abandon
✅ 1246 auto-abandon
✅ 1212 auto-abandon
✅ 1210 auto-abandon
✅ 1200 auto-abandon
✅ 1197 auto-abandon
✅ 1177 auto-abandon
✅ 1161 auto-abandon
✅ 1146 auto-abandon; extension-data-PrivPrev; TypeSpec data
✅ 1142 auto-abandon
✅ 1113 auto-abandon
✅ 1062 auto-abandon
✅ 1035 auto-abandon
✅ 1033 auto-abandon; retired before GA; retiring the service under process
✅ 1030 auto-abandon
✅ 1101 auto-abandon
✅ 1041 auto-abandon
✅ 1067 auto-abandon
✅ 1088 auto-abandon
✅ 1057 auto-abandon
✅ 1097 auto-abandon
✅ 1313 auto-complete
✅ 1302 auto-complete
✅ 1259 auto-complete
✅ 1244 auto-complete
✅ 1243 auto-complete
✅ 1241 auto-complete
✅ 1230 auto-complete
✅ 1229 auto-complete
✅ 1224 auto-complete
✅ 1214 auto-complete
✅ 1199 auto-complete
✅ 1193 auto-complete
✅ 1189 auto-complete
✅ 1124 auto-complete
✅ 1038 auto-complete
✅ 1096 auto-complete
✅ 1039 auto-complete
✅ 1050 auto-complete
maririos commented 1 month ago

@ladonnaq what do you recommend to do for the completed Release plans? Current information is not accurate, but overwritting DB might cause the same as we won't have all information or dates correctly.

Maybe something we can do is complete the Release plans on the DB and add something in the release plan work item that identifies the release plan as closed automatically. A label? a comment? a field?

What do you think will be more easier to query and mantain?

ladonnaq commented 3 weeks ago

@ladonnaq what do you recommend to do for the completed Release plans? Current information is not accurate, but overwritting DB might cause the same as we won't have all information or dates correctly.

Maybe something we can do is complete the Release plans on the DB and add something in the release plan work item that identifies the release plan as closed automatically. A label? a comment? a field?

What do you think will be more easier to query and mantain?

@maririos Go ahead and mark the release plans as complete in the DB and for the Release Plan work item do the following:

maririos commented 3 weeks ago
  • Change the state to "Finished"
  • [ ] Add tag "auto-closed"

Ok. I have created automation for this to work. Once this is in prod I will start marking all the selected issues as completed. More details on implementation here: https://github.com/Azure/azure-sdk-tools/issues/8872

maririos commented 1 week ago

Improvement to this process is tracked: https://github.com/Azure/azure-sdk-tools/issues/8921

maririos commented 2 days ago

All done