Skip to content

Instantly share code, notes, and snippets.

@Wilto

Wilto/gist:eddfd4e3d56ed9a12e0e

Created November 24, 2014 19:31
Show Gist options

  • Select an option

    Learn more about clone URLs
  • Save Wilto/eddfd4e3d56ed9a12e0e to your computer and use it in GitHub Desktop.

Select an option

Learn more about clone URLs
Save Wilto/eddfd4e3d56ed9a12e0e to your computer and use it in GitHub Desktop.
Download ZIP
Semver-esque
Raw
gistfile1.md
  1. MAJOR version at maintaners’ discretion (refactoring core)
  2. MINOR version when you make improvements in a backwards-compatible manner (performance)
  3. PATCH version when you make backwards-compatible bug fixes (spec compliance)

Polyfills don’t have “breaking changes” (or at least they shouldn’t), so I’m wondering what makes sense for major versions. “Whenever we do a lot of things” doesn’t seem particularly nailed-down, but I’m not sure there’s a better way.

@Wilto
Copy link
Copy Markdown
Author

Wilto commented Nov 24, 2014

Yeah—I’m just thinking we’re well into “stable spec” territory now on Picturefill, so that might not apply here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment