✅ supervision-0.13.0 checklist

[SkalskiP]

overview

Hi everyone 👋🏻! Time to plan supervision-0.13.0 release. It looks like (once again) we will have many external contributors. 🔥 I have written down the tasks we plan to carry out and those who initially signaled that they want to contribute. Don't take this as binding. I'm just trying to plan the scope of work.

note

• All issues and pull requests related to supervision-0.13.0 release got marked with version: 0.13.0 label and are pinned to version: 0.13.0 milestone.
• Please be patient. 🙏🏻 I love to work on supervision, but I have many other responsibilities. I always try to be as responsive as possible.

checklist

• annotators redesign by @hardikdava and @SkalskiP
  • redesigned annotators #170
  • Unicode Label Support #143
  • Advanced BoxAnnotator🤩 #168
  • Add object trace annotation to Supervision 🤩 #49
• tracking support by @dbroboflow
  • Tracking support #195
  • Tracker #203
• fix sv.DetectionDataset.as_coco polygon output by @mayankagarwals
  • Format coco output data as per standard #225
  • coco segmentation data for polygon should be [polygon,] not polygon #205
• PaddlePaddle integration by @hardikdava
  • Paddledet support #191
  • PaddleDetection Support #187
• Ultralytics integration by @hardikdava
  • Feature/ultralytics all models #222
  • Ultralytics all model support for detections #221
• Show Progress in time-consuming tasks by @mayankagarwals
  • Show Progress in time consuming tasks #183
• Add support for loading segmentation datasets in Pascal VOC format by @kirilllzaitsev
• Building test package versions from the develop branch using GitHub actions by @onuralpszr
• Use pre-commit to automate code formatting by @onuralpszr
• object detection mAP calculation by @hardikdava
  • Object detection mAP score #232

Please let me know in the comment if I forgot or mixed up anything. 🙏🏻

[onuralpszr]

Automatic Github action stable release trigger using git tags ( tag example v0.13.0 since we already have tags let's keep them in use as well), for stable releases. Since we going to make "develop" release let's also make that for stable too. That means no more manual builds

[SkalskiP]

@onuralpszr, what would be the triggering mechanism? I do the commands below, and it triggers package build?

git tag 0.13.0-alpha
git push origin --tags

[onuralpszr]

Yes, change your version in toml and add tag then push and action will start.

[SkalskiP]

Would that be possible to get away with only tagging? That would be awesome to drop the extra step.