I feel like this article can be easily applied to Meteor’s versioning strategy too
If Meteor doesn’t want to use big numbers, or year based versioning, they could use cool code-names for big releases to help build up hype again
I feel like this article can be easily applied to Meteor’s versioning strategy too
If Meteor doesn’t want to use big numbers, or year based versioning, they could use cool code-names for big releases to help build up hype again