Revised Roadmap to 1.0.0 and beyond

[d-chambers]

@andreas-wuestefeld mentioned in #637 DASCore should probably be 1.0.0 by now. I think he is right, so I wanted to revise the #637 post here with some high-level features mapped to their anticipated version. To improve user experience, starting on 1.0.0, we will release alpha versions whenever there are breaking changes in order to give folks ample time to test and adjust code. Hopefully 1.0.0 will be the only one, and even then the breaking changes will be minor.

Here is my tentative plan:

1.0.0

• Support for remote files (S3, github, etc), already in dev
• Refactor spool backend and unified machinery (in spool-index-backed, see Dascore 0.2.0 #637, will close a bunch of issues)
• Resolve slope_filter open bounds, signed velocities, and slowness-based bounds #708 and make any breaking changes to API needed.
• Resolve Patch coordinate/channel alignment #706 and issue guidelines about the meaning of the coordinates
• String coordinages (already in dev)
• API for hdf compression and generic codecs ( Better API for DASDAE compression #734)

1.1.0

• Inventory and spool integration ( see https://github.com/DASDAE/inventory). Still more details to sort out here, but it will be a big win.

1.2.0 (or maybe 2.0?)

• Refactor patch functions to support array api, probably breaking existing patch functions into classes and separating metadata and array ops to enable compilation by Jax, and probably pytorch (see https://github.com/DASDAE/dasjax for a proof of concept). Also calculating fingerprints for patch operations instances and a better provenance tracking story.