# delphi-etl-apps-proto

This library provides classes to work with Delphi data serialized to protobuf.

# Usage

The library is available in Delphi Nexus:
* https://artifacts.apollo.stream/
* https://artifacts-internal.delphiplatform.io

#### Scala
Supported binary versions:
* `2.11`
* `2.12`

```scala
libraryDependencies += "com.sonymusic" %% "delphi-etl-apps-proto" % "1.2.0"
```


#### Java
```xml
<dependency>
    <groupId>com.sonymusic</groupId>
    <artifactId>delphi-etl-apps-proto_2.11</artifactId>
    <version>1.2.0</version>
</dependency>
```
or 
```xml
<dependency>
    <groupId>com.sonymusic</groupId>
    <artifactId>delphi-etl-apps-proto_2.12</artifactId>
    <version>1.2.0</version>
</dependency>
```

# Development Process
## Branching Strategy
This project follows so-called "Feature Branching Strategy". It means, that all changes should be implemented in a
separate branch and then merged into the target branch after review and approval by other teammates.

All branches should have a Jira ticket number in their names. Additional information about the changes in that branch
is welcomed, but not obligatory.

Examples of good branch naming:
* `task/XXX-1111/readme-update`
* `bug/XXX-1111/test-aggregation`
* `XXX-1111/naming-fixes`
* `XXX-1111`

> :information_source: _Since, this project does not require frequent changes and active development process, we have only one default
branch: `master`. All PRs should be targeted to it._

### Typical development workflow
The typical day-to-day flow includes normal changes that developers make to the code, changes that do not bring any
heightened sense of urgency.
* The branch should be crated from the `master` branch.
* PR should be targeted and merged to the `master` branch.
* Version update is required (e.g. `1.2.0` -> `1.3.0`).