4 ms·
Not sure if you should rely on SemVer for maturity estimates either, though. I guess it can be one signal, but I wouldn't say a very useful one.
by elsurudo 7y ago
Not sure if you should rely on SemVer for maturity estimates either, though. I guess it can be one signal, but I wouldn't say a very useful one.
- itake 7y agowhat would be a more reliable way to know?
- codetrotter 7y agoLook at the following: - Number of commits. - Number of open issues. - Number of closed issues. - How they respond to issues. - Are the commit messages descriptive? - Is the codebase a mess or does it look reasonable?
- deleted 7y ago[deleted]
- LoSboccacc 7y agoyeah is 1.7 a very stable 1.x or a very immature 2.x? what is 0.7 then? and 2.0? can't answer one and the other consistently. it's great for compatibility level, and that's that.
- ppseafield 7y agoIndeed, React got to version 0.14.x before the major number became 15 after a total of three years since the first public release.
- paulddraper 7y agoIf anything, calendar version is superior here because you can tell when it was updated (and if it follows modern conventions, techniques, etc.)