Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Give the spec a version? #10

Open
DavidBuchanan314 opened this issue Feb 6, 2025 · 1 comment
Open

Give the spec a version? #10

DavidBuchanan314 opened this issue Feb 6, 2025 · 1 comment

Comments

@DavidBuchanan314
Copy link
Contributor

DavidBuchanan314 commented Feb 6, 2025

I don't imagine there'd need to be any significant changes to the core phc-string-format spec going forwards, but just in case, I think it'd be worthwhile to give the spec a version - so a library can say in its documentation that it implements a particular version. To be clear, this would have no impact on the format itself.

Given the relative maturity/completeness of the spec at this point, v1.0.0 feels appropriate (if using semver, in line with C2SP specs)

@tarcieri
Copy link
Contributor

tarcieri commented Feb 7, 2025

That sounds okay to me as the only person currently maintaining this. It might also make sense to upstream to C2SP.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants