Requirements for v1.0 Release

[pxp928]

Opening this issue to discuss what are the important features that need to be added or stabilized in order for a 1.0 release for GUAC.

Based on initial feedback:

• API stability

  • track based on days since API change, and when that hits 3 months without a change, we can consider it stable for a v1.0 release

• At least 1 supported and recommended persistent and optimized, backend

  • Tested on small, medium, large datasets on some standardized hardware
  • track performance on highly used queries (TBD) and determine the acceptable time to completion

• Upgrade path to 2.0 when it is out (how to get the data out to a 2.0 instance)

• Ingestors - EITHER OR

  • Have a test suite for X documents that are generated from Y tooling/pipelines
  • Solve the NATS issue where we would have a centralized ingestor

• Some set of use cases satisfied (TBD)

[pxp928]

We also need an answer/implementation for the software identifier problem for v1.0 @SantiagoTorres and @mlieberman85 .

[pxp928]

API changes include: https://github.com/guacsec/guac/issues/1261, #1196, #1197, #1198