spdx / ntia-conformance-checker

Check SPDX SBOM for NTIA minimum elements

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Spelling: Minimum vs mininum

thireo opened this issue · comments

There's a small spelling mistake in the function ntia_mininum_elements_compliant and therefore also in the README.

Suggestion:
ntia_minimum_elements_compliant

@thireo, thank you for the bug report. PR's welcome

But this will be a breaking change, won't it? @goneall, should I bump the version to 2.x? What do you advise? This silly typo is definitely my fault. Oops.

Let me know if I need to change anything in my PR or commit.
I'm not entirely sure of the correct way of doing this.

Thank you, @thireo. One minor request: Can you please use the black formatter? See the PR thread for further info.

@goneall -- friendly ping. What do you think is the best approach to handling this breaking change?

@jspeed-meyers - yes, probably a breaking change - even though pretty minor. Since it is breaking, we should probably go to the next major version number. Is there any other planned changes that may be breaking we should include in a major release?

@goneall: I don't currently have any plans for other breaking changes. Given that, should we delay cutting a new release for a couple of months just to see if there any other breaking changes? Or should I merge the associated PR here and cut a release ASAP?

I'll make sure the release notes clearly explain this change, BTW.

should I merge the associated PR here and cut a release ASAP?

Unless @thireo would like these changes merged in quickly, I think we should wait 3 to 4 weeks and see if there are any other breaking changes.

I added a 2.0.0 milestone to the project, so we can tag any PR's and Issues with the release milestone.

@thireo - OK to wait a month or two for this fix?

Thank you for the wise advice, @goneall. And thank you for creating the 2.0.0 milestone. That sounds like a plan to me.

I'm okay waiting a month for this to be merged. I'll just use my own patch meanwhile :)

Okay, I merged this fix. But I will not cut a version until early April.