Scuba 3.0

[JonathonReinhart]

(This thread was migrated from Gitter.)

---

I'd like to talk about releasing Scuba 3.0. Scuba follows semver so any major, breaking changes should be accompanied by a major version bump.

There have already been breaking changes:

• Fixing Scuba Runs the Entrypoint Before Every Command #114 required what I would consider a breaking change: Don't run the entrypoint for each line in a multi-line script #121.
• I dropped support for Python 2.6, 3.2, and 3.3
  • I'd also like to drop support for Python 2.7

Luckily, none of those changes should really affect most users.

I just merged #137 which provides a (somewhat ugly) workaround for the fact that I used . as the "key separator" in the !from_yml constructor, even though . is a valid character in YML keys (and has special meaning in .gitlab-ci.yml). I wish I had instead used :.

I could avoid backwards incompatibility at all I were to add a version key to the Scuba YML spec which says:

• Use new entrypoint semantics
• Use : as the separator instead of .

Thoughts?

[JonathonReinhart]

From user ???

That seems like a reasonable solution to me. Perhaps you could add some sort of deprecation warning to completely remove support for using . as a "key separator" in a future major rev bump?

[JonathonReinhart]

We decided to avoid any major version/compatibility issues for now.

• We decided Don't run the entrypoint for each line in a multi-line script #121 is not a breaking change; rather it corrected the expected behavior.
• Dropping support for older versions of Python doesn't warrant a major version change (even in a SemVer library)
• config: Update !from_yml to handle complex keys #137 is "good enough" for now