scorecard icon indicating copy to clipboard operation
scorecard copied to clipboard
verified publisher icon ossf

DISCUSSION: v5 milestone

Open laurentsimon opened this issue 4 years ago • 12 comments

Let's start collecting and tagging issues with the v5 milestone.

  • badges
  • raw results (beta release)

laurentsimon avatar Jan 19 '22 17:01 laurentsimon

cc @azeemsgoogle @naveensrinivasan

laurentsimon avatar Jan 19 '22 17:01 laurentsimon

One item I would add here is deprecation of v1 (pass/fail) code in this release.

azeemshaikh38 avatar Feb 11 '22 19:02 azeemshaikh38

  • #1393

azeemshaikh38 avatar Feb 11 '22 19:02 azeemshaikh38

Adding few more:

  • #1618
  • #1597
  • #1032
  • #575
  • #1537
  • #271
  • #1389
  • #1245

azeemshaikh38 avatar Feb 13 '22 05:02 azeemshaikh38

Updating this after discussion on the bi-weekly. @justaugustus to add an issue about release process for Scorecard along with the items mentioned above.

azeemshaikh38 avatar Feb 24 '22 22:02 azeemshaikh38

Updating this after discussion on the bi-weekly. @justaugustus to add an issue about release process for Scorecard along with the items mentioned above.

Added to https://github.com/ossf/scorecard/issues/1553 as https://github.com/ossf/scorecard/issues/1676!

justaugustus avatar Feb 24 '22 23:02 justaugustus

Unless there are objections, I'm volunteering as tribute/the Release Manager for socrecard v5 :) It'll give me an opportunity to think through design and process improvements as we get closer to the release date.

From https://github.com/ossf/scorecard/issues/1680#issuecomment-1053587529:

I think we should instead declare that the next major release version (v5.0.0) is the first release in which we will be SemVer-compliant and direct our efforts into designing the module in a way that we can ensure that.

I've created a tracking issue for this and added it to the v5 milestone: https://github.com/ossf/scorecard/issues/1683

justaugustus avatar Feb 27 '22 15:02 justaugustus

Unless there are objections, I'm volunteering as tribute/the Release Manager for socrecard v5 :) It'll give me an opportunity to think through design and process improvements as we get closer to the release date.

From #1680 (comment):

I think we should instead declare that the next major release version (v5.0.0) is the first release in which we will be SemVer-compliant and direct our efforts into designing the module in a way that we can ensure that.

I've created a tracking issue for this and added it to the v5 milestone: #1683

+1

naveensrinivasan avatar Feb 27 '22 15:02 naveensrinivasan

@ossf/scorecard-maintainers - we have most features implemented here to start thinking about having a v5 release. What do folks think? @justaugustus your input here as the release manager for Scorecard v5 would be very much appreciated :)

azeemshaikh38 avatar Aug 16 '22 21:08 azeemshaikh38

@ossf/scorecard-maintainers - we have most features implemented here to start thinking about having a v5 release. What do folks think? @justaugustus your input here as the release manager for Scorecard v5 would be very much appreciated :)

👍 This would be a good time to release.

  • Scorecards badges
  • Scorecards API
  • Go 1.18 migration

naveensrinivasan avatar Aug 16 '22 21:08 naveensrinivasan

This issue is stale because it has been open for 60 days with no activity.

github-actions[bot] avatar Nov 03 '23 01:11 github-actions[bot]