Lines Matching +full:check +full:- +full:api +full:- +full:compatibility

11 …`#coroutines` channel in [KotlinLang Slack](https://surveys.jetbrains.com/s3/kotlin-slack-sign-up).
27     run the [Knit tool](#running-the-knit-tool) and commit the resulting changes as well. 
29 …sive rewrites/additions to the docs, then please [contact the maintainers](#contacting-maintainers)
32 …* Follow the [Kotlin Coding Conventions](https://kotlinlang.org/docs/reference/coding-conventions.…
47 …PRs that add new API without a corresponding issue with positive feedback about the proposed imple…
51 …* [Update the public API dumps](#updating-the-public-api-dump) and commit the resulting changes as…
53 …* If you plan large API additions, then please start by submitting an issue with the proposed API …
55   * [Contact the maintainers](#contacting-maintainers) to coordinate any extensive work in advance.
62 * Run `./gradlew <module>:check` to test the module you are looking at to speed 
67 to Gradle (in Preferences -> Build, Execution, Deployment -> Build Tools -> Gradle -> Build and run…
72 * JDK 1.8 referred to by the `JDK_18` environment variable. Only used by nightly stress-tests. 
73   It is OK to have `JDK_18` point to a non-1.8 JDK (e.g. `JAVA_HOME`) for external contributions.
83 * Use [Knit](https://github.com/Kotlin/kotlinx-knit/blob/main/README.md) for updates to documentati…
87 ### Updating the public API dump
89 …he [Binary Compatibility Validator](https://github.com/Kotlin/binary-compatibility-validator/blob/…
90   * Run `./gradlew apiDump` to update API index files. 
91   * Commit the updated API indexes together with other changes.
99 …ing cannot be done, not convenient, or does not work &mdash; submit an [issue](#submitting-issues).