Release all drivers (except nirfsg): nidcpower 1.6.0, others 1.5.0

[mohit-emerson]

• This contribution adheres to CONTRIBUTING.md.
• I've updated CHANGELOG.md if applicable.
• I've added tests applicable for this pull request

What does this Pull Request accomplish?

Releases all drivers in repo, bump up minor version.

See CHANGELOG.md for list of changes

• nidcpower 1.6.0
• nidigital 1.5.0
• nidmm 1.5.0
• nifgen 1.5.0
• nimodinst 1.5.0
• niscope 1.5.0
• nise 1.5.0
• niswitch 1.5.0
• nitclk 1.5.0

List issues fixed by this Pull Request below, if any.

None

What testing has been done?

PR Validations

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 89.32%. Comparing base (d369566) to head (d222073).

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #2186   +/-   ##
=======================================
  Coverage   89.32%   89.32%           
=======================================
  Files          73       73           
  Lines       19048    19048           
=======================================
+ Hits        17014    17015    +1     
+ Misses       2034     2033    -1     

Flag	Coverage Δ
codegenunittests	84.90% <ø> (ø)
nidcpowersystemtests	94.38% <ø> (+0.04%)	⬆️
nidcpowerunittests	89.53% <ø> (ø)
nidigitalsystemtests	92.02% <ø> (ø)
nidigitalunittests	68.44% <ø> (ø)
nidmmsystemtests	92.29% <ø> (ø)
nifakeunittests	86.01% <100.00%> (ø)
nifgensystemtests	94.32% <ø> (ø)
nimodinstsystemtests	73.85% <ø> (ø)
nimodinstunittests	94.20% <ø> (ø)
nirfsgsystemtests	81.12% <ø> (ø)
niscopesystemtests	89.96% <ø> (ø)
niscopeunittests	43.20% <ø> (ø)
nisesystemtests	91.50% <ø> (ø)
niswitchsystemtests	81.56% <ø> (ø)
nitclksystemtests	94.87% <ø> (ø)
nitclkunittests	98.26% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines	Coverage Δ
generated/nifake/nifake/__init__.py	84.72% <100.00%> (ø)

... and 1 file with indirect coverage changes

---

Continue to review full report in Codecov by Harness.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d369566...d222073. Read the comment docs.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[vnktshr21]

Version tested against should be updated first to latest drivers once published. That should be PR of it's own and should merge before these release changes.

[vnktshr21]

PR title is not detailed enough

[ni-jfitzger]

You'll probably need me to publish some of these releases to pypi. Let me know.

[vnktshr21]

publish the PR once ready

[vnktshr21]

@ni-jfitzger , we are upgrading the minor version for all drivers instead of patch version, which, some of the previous API releases followed for few drivers. Is this fine? For RFSG, it has been minor version bumps since the first release.

[ni-jfitzger]

@ni-jfitzger , we are upgrading the minor version for all drivers instead of patch version, which, some of the previous API releases followed for few drivers. Is this fine? For RFSG, it has been minor version bumps since the first release.

I think the dropping of old Python Support merits a major version bump, though @marcoskirsch is free to disagree. I'm a little bit on the fence about it, honestly, because we restrict the Python version in setup.py, already to keep from breaking users.
Adding new Python Support or new functionality definitely merits a minor bump, rather than just a patch bump, which is really just used for backward-compatible bug fixes.

[mohit-emerson]

@ni-jfitzger @vnktshr21 . We've released RFSG 1.2.0 separately (hence its changes removed from this PR). For the rest of drivers upgraded major version to 2.0.0.

[ni-jfitzger]

@ni-jfitzger @vnktshr21 . We've released RFSG 1.2.0 separately (hence its changes removed from this PR). For the rest of drivers upgraded major version to 2.0.0.

Sorry, I'm having second thoughts about the major version bump.
Even if other projects do it, which they may or may not, we've never done that and a major version bump is likely to send the wrong message.

I shouldn't listen to Copilot for these things.

[bkeryan]

@ni-jfitzger , we are upgrading the minor version for all drivers instead of patch version, which, some of the previous API releases followed for few drivers. Is this fine? For RFSG, it has been minor version bumps since the first release.

I think the dropping of old Python Support merits a major version bump, though @marcoskirsch is free to disagree. I'm a little bit on the fence about it, honestly, because we restrict the Python version in setup.py, already to keep from breaking users. Adding new Python Support or new functionality definitely merits a minor bump, rather than just a patch bump, which is really just used for backward-compatible bug fixes.

@mshafer-NI We don't bump major to drop old Python versions, right?

Python tooling ensures that users cannot install a package version that is incompatible with their current Python version.

[mshafer-NI]

@ni-jfitzger , we are upgrading the minor version for all drivers instead of patch version, which, some of the previous API releases followed for few drivers. Is this fine? For RFSG, it has been minor version bumps since the first release.

I think the dropping of old Python Support merits a major version bump, though @marcoskirsch is free to disagree. I'm a little bit on the fence about it, honestly, because we restrict the Python version in setup.py, already to keep from breaking users. Adding new Python Support or new functionality definitely merits a minor bump, rather than just a patch bump, which is really just used for backward-compatible bug fixes.

@mshafer-NI We don't bump major to drop old Python versions, right?

Python tooling ensures that users cannot install a package version that is incompatible with their current Python version.

We normally bump minor for dropping old Python versions. There's an argument for that being a "breaking change" since users of the old Python can't use the newer version; however, most Python packages don't treat it that way.

[mohit-emerson]

Reverted back to minor version upgrades. @ni-jfitzger , Can you retrigger rhel run?
Once it completes please proceed with merging and handle the PyPI publishing. Thanks