Lines Matching +full:update +full:- +full:docs +full:- +full:branch

11 …`#coroutines` channel in [KotlinLang Slack](https://surveys.jetbrains.com/s3/kotlin-slack-sign-up).
19 * All development (both new features and bug fixes) is performed in the `develop` branch.
20   * The `master` branch contains the sources of the most recently released version.
21   * Base your PRs against the `develop` branch.
22   * The `develop` branch is pushed to the `master` branch during release.
23   * Documentation in markdown files can be updated directly in the `master` branch, 
26 …* After fixing/changing code examples in the [`docs`](docs) folder or updating any references in t…
27     run the [Knit tool](#running-the-knit-tool) and commit the resulting changes as well. 
29 …If you plan extensive rewrites/additions to the docs, then please [contact the maintainers](#conta…
32 …* Follow the [Kotlin Coding Conventions](https://kotlinlang.org/docs/reference/coding-conventions.…
51 …* [Update the public API dumps](#updating-the-public-api-dump) and commit the resulting changes as…
55   * [Contact the maintainers](#contacting-maintainers) to coordinate any extensive work in advance.
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…
84   * Run `./gradlew knit` to update the example files, links, tables of content.
89 * Use the [Binary Compatibility Validator](https://github.com/Kotlin/binary-compatibility-validator…
90   * Run `./gradlew apiDump` to update API index files. 
99 …ing cannot be done, not convenient, or does not work — submit an [issue](#submitting-issues).