Why We Should Use Semantic Versioning
I think it's time for WuzAPI to adopt semantic versioning. Right now, the project is in great shape and has a solid community, but we're missing a clear versioning scheme. Here's why I think this would help:
What's the problem?
- Users don't know what changed between versions (was it a breaking change or just a patch?)
- Developers depending on WuzAPI can't safely pin versions knowing they'll get important updates
- It's hard to track what's been fixed, what's new, and what might break your setup
- When someone asks "what version am I running?", there's no clear answer
What would change?
- We start tagging releases like
v1.0.0, v1.1.0, v1.2.0, etc.
- Each tag clearly indicates: major changes (breaking), minor changes (new features), or patches (bug fixes)
- We keep a changelog so people know exactly what they're getting
Why it matters
- Package managers, Docker registries, and dependency tools all expect this
- Users running WuzAPI in production can upgrade confidently
- Contributors get a clearer picture of the project's evolution
- It just makes the project feel more stable and mature
This doesn't require a lot of work—mostly just being consistent about tagging releases going forward. I think it's a natural next step for WuzAPI.
Why We Should Use Semantic Versioning
I think it's time for WuzAPI to adopt semantic versioning. Right now, the project is in great shape and has a solid community, but we're missing a clear versioning scheme. Here's why I think this would help:
What's the problem?
What would change?
v1.0.0,v1.1.0,v1.2.0, etc.Why it matters
This doesn't require a lot of work—mostly just being consistent about tagging releases going forward. I think it's a natural next step for WuzAPI.