Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Too old to be a <1.0.0 release version
See original GitHub issueI’d like to rely on this software for important world changing projects, but it’s still in 0.X version which means minor version bumps include breaking changes which is not good.
Are there any plans to bump to 1.X so I can pin to trafaret>=1,<2? I’d like some sort of agreement of stability before I include start using this to change the world.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:1
- Comments:5 (3 by maintainers)
Top Results From Across the Web
What is the significance of reaching major version 1.0.0?
If the project is using Semantic Versioning, then a 1.0. 0 release means that the public API is stable. Not having a stable...
Read more >The myth that releasing version 1.0.0 implies any type of long ...
It does not imply anything other than breaking changes. It is as much quality or long term support as any other version increase....
Read more >What to use as an initial version? [closed] - Stack Overflow
Version 1.0.0 defines the public API. The way in which the version number is incremented after this release is dependent on this public...
Read more >Why I don't start versions at 0.x any more
SemVer is pretty clear about pre-releases. Any version with a major version of 0 is considered “initial development”, and anything can change at ......
Read more >I just released a version 0.0.1, but have found a backwards ...
Last week I finished my first open source library and released it at version 0.0.1. My understanding is that you are supposed to...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Ok, lets 1.0.0.
I understand @Deepwalker concerns: aiohttp after 1.0 release has several breaking API changes. On other hand claiming a stable release forces to change development process: deprecation warnings, stable API support etc.