<commit_before>## json4s Contributers' Guide

### Issues

- Questions should be posted to [stackoverflow.com](http://stackoverflow.com/questions/tagged/json4s)
- Please describe about your issue in detail (verison, situation, examples)
- We may close your issue when we have no plan to take action right now. We appreciate your understanding.

### Pull Requests

- Pull requests basically should be sent toward "3.6" branch
- Source/binary compatibility always must be kept as far as possible
- Prefer creating scala source code for each class/object/trait (of course, except for sealed trait)
- json4s build checks binary compatibility by using [MiMa](https://github.com/typesafehub/migration-manager/wiki/Sbt-plugin) for maintenance releases (e.g. 3.3.x).

#### Branches

##### 3.6 (the default branch)

- The latest stable version
- This branch must be able to build against Scala 2.10, 2.11 and 2.12
- This branch requires Java 8+ for all Scala versions

##### 3.5

- The version 3.5 series maintainance branch
- This branch must be able to build against Scala 2.10, 2.11 and 2.12

##### 3.4

- The version 3.4 series maintainance branch
- All the backports must be source/binary compatibility
- This branch must be able to build against Scala 2.10 and 2.11

##### 3.3

- The version 3.3 series maintainance branch
- All the backports must be source/binary compatibility
- This branch must be able to build against Scala 2.10 and 2.11

#### Testing your pull request

All the pull requests must pass the Travis CI jobs before merging them.

https://travis-ci.org/json4s/json4s

Testing with default settings is required when push changes:

```sh
sbt test
```<commit_msg>Add 2.13.0-M4 to the supported Scala versions<commit_after>## json4s Contributers' Guide

### Issues

- Questions should be posted to [stackoverflow.com](http://stackoverflow.com/questions/tagged/json4s)
- Please describe about your issue in detail (verison, situation, examples)
- We may close your issue when we have no plan to take action right now. We appreciate your understanding.

### Pull Requests

- Pull requests basically should be sent toward "3.6" branch
- Source/binary compatibility always must be kept as far as possible
- Prefer creating scala source code for each class/object/trait (of course, except for sealed trait)
- json4s build checks binary compatibility by using [MiMa](https://github.com/typesafehub/migration-manager/wiki/Sbt-plugin) for maintenance releases (e.g. 3.3.x).

#### Branches

##### 3.6 (the default branch)

- The latest stable version
- This branch must be able to build against Scala 2.10, 2.11, 2.12, and 2.13.0-M4
- This branch requires Java 8+ for all Scala versions

##### 3.5

- The version 3.5 series maintainance branch
- This branch must be able to build against Scala 2.10, 2.11 and 2.12

##### 3.4

- The version 3.4 series maintainance branch
- All the backports must be source/binary compatibility
- This branch must be able to build against Scala 2.10 and 2.11

##### 3.3

- The version 3.3 series maintainance branch
- All the backports must be source/binary compatibility
- This branch must be able to build against Scala 2.10 and 2.11

#### Testing your pull request

All the pull requests must pass the Travis CI jobs before merging them.

https://travis-ci.org/json4s/json4s

Testing with default settings is required when push changes:

```sh
sbt test
```
{'fraction_non_alphanumeric': 0.08785377358490566, 'fraction_numerical': 0.0347877358490566, 'mean_word_length': 3.946064139941691, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 4, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '7609663', 'n_tokens_mistral': 1041, 'n_tokens_neox': 954, 'n_words': 449}