Billy Autrey

So for this task, I'm planning to deprecate first (to prevent sudden usage breaks). Do we want to remove _all_ of the postfix symbol operators and refer back to `updated`?...

In #11672, I opted to do the following: * Add multiple signatures for `updated`, to reflect all the current usages of `+` * Also, add the same signatures for `removed`,...

So far, looks like @jtjeferreira is working on at least slash syntax for this: https://github.com/sbt/sbt-native-packager/pull/1636

Have you seen this? https://www.scala-sbt.org/2.x/docs/en/changes/migrating-from-sbt-1.x.html#the-plugincompat-technique Obviously not exhaustive, I'm running into a similar issue that needs more implicit conversions than listed in this example. But it's a little more future...

Testing sbt is also very custom - I assume you would want the ability to run `scripted`?

We'll likely want to cross-publish to `sbt 2.0` with this as well. https://github.com/sbt/sbt-git/issues/257

That document outlines _several_ features that you want implemented. Is the goal to port in all of these features, or none at all? Maybe it's worth separating out the discussion...

~I assume the inspiration here is Bazel's persistent local workers?~ It's in the first paragraph of the RFP 😆 I'll take a look at the RFP. I assume this also...

The desired UX is a bit of a question mark here. Bazel needs persistent workers for JVM tasks because it doesn't have a single server/shell that runs in an interactive...

Breaking this down into subtasks, then, here's what I'm seeing: * Implement the general purpose persistent worker API so that spawned workers can take on work and report status. *...