This is an ambitious project with a massive scope, so there are no plans to squish this all into a single GitHub repository. For now, this whole project will be managed here on Notion. Especially until we reach a stable 1.0, changes to any part of the project will likely drive changes in others, so it’s unlikely that we will use GitHub issue tracking any time soon.
I’ll have some more details coming soon to this page about how the Notion space is laid out, and what our decision-making process is, once we actually have one.
The current plan is for entire Veneto ecosystem to share releases with a major.minor versioning scheme, conforming to semantic versioning, where breaking changes drive a major version and non-breaking changes drive a minor version. Since patches will generally be applied to specific repositories one-at-a-time, individual repositories will have a full major.minor.patch version.
But this definitely won’t work if we need to make breaking API changes to a component (like the parser) that’s not driven by changes to the language itself or the rest of the ecosystem. Gotta think this through
Making a final decision on this is tracked in v1.0.0 Stability. Until then it’s all unstable then anyways