There should be a stable 1.0 release about lens HOT 3 CLOSED

@AlexKnauth - Can you think of anything else that's required before 1.0?

from lens.

@AlexKnauth This is what I'm thinking with regards to versioning post-1.0:

• Nothing in the lens or a lens/* collection should break backwards compatibility. Non exhaustive list of backwards-incompatible changes:
  • Renaming or removing an export
  • Renaming or removing a subcollection
  • Changing the behavior of an export in any way such that what used to be valid non-error-ing uses of the export would behave differently
  • Moving an export from one subcollection to another (it should be re-provided instead)
• New features should bump the major version. Once a new feature makes it into the main collection, it must commit to backwards compatibility. To add a new feature that you wish to allow backwards incompatible changes to, add it to unstable/lens instead of lens. This should bump the minor version.
• Bugfixes and other minor behavioral changes to existing code that are visible to users of the package should bump the minor version.
• Documentation changes, refactoring, added tests, reorganizations, etc. etc. do not need to bump the version provided it isn't practically possible for a user of the collection to tell the change happened.

This would lead to a pattern where new exports would get added in "batches", as they are iterated on in the unstable collection until it's decided there's enough new stable features to justify bumping the major version.

from lens.

Bumping the version to 1.0 now.

from lens.