-
-
Notifications
You must be signed in to change notification settings - Fork 513
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide migration guides #142
Comments
Example of other project doing this: Ember.js Deprecations, collected for a release series (2.x): https://www.emberjs.com/deprecations/ember-data/v2.x/ |
See also: cucumber/cucumber-jvm#1478 |
ElasticSearch has a nice overview of release notes / breaking changes, for example: https://www.elastic.co/guide/en/elasticsearch/reference/current/breaking-changes-6.3.html |
The linked article is 404. |
Migration info for deprecated classes (as of cucumber-jvm v4.5.x): import io.cucumber.junit.CucumberOptions |
@NikolaZag |
We're now doing this in cucumber ruby / jvm and in general are using the repo's proper for more technical docs. So closing this off as completed. |
Proposal: When making large/breaking changes in new versions, provide a migration guide on how to upgrade to the new version.
In general, mention semver versioning (when people can expect breaking changes) and where to find information about (breaking) changes in a new version.
Examples:
With IntelliJ: The need to upgrade to newer version of Cucumber for Java plugin to prevent error with the Formatter
The text was updated successfully, but these errors were encountered: