Major Release

[reactivex]

Major Release

[benjchristensen]

We can copy over the new build/release config from RxJava in these locations:

• https://github.com/ReactiveX/RxJava/tree/1.x/gradle
• https://github.com/ReactiveX/RxJava/blob/1.x/.travis.yml

Then I can update the .travis.yml file with the encrypted credentials for Bintray and Sonatype. Then you can build and release just via git tags via Travis.

[benjchristensen]

I think it's ready to go. Let me know when the code is ready to release and I can do the first one so I can debug through any issues.

What version number do you want for this, 1.0.0?

[MarioAriasC]

@benjchristensen Thanks for the info, let me discuss it with the community

@cy6erGn0m @orangy @abreslav @hhariri do we want this to version 1.0.0? Probably we want something to said that is compatible with version M11 and so on

[orangy]

What is current version of RxJava? We probably want major/minor to match RxJava, and then use 3rd number to reflect Kotlin Milestone. E.g. if RxJava is 1.5, for M11 it would be 1.5.11

[benjchristensen]

RxJava is at 1.0.8: https://github.com/ReactiveX/RxJava/releases

[benjchristensen]

Trying to track the RxJava version would be difficult to do reliably as every patch release would require a release of RxKotlin. Also, that approach would fall apart the first time you need to release without RxJava having released. Or if you need to do a breaking change that bumps RxKotlin to 2.0.

The various projects are decoupled so they can have different lifecycles.

[orangy]

I see, makes sense. Then probably keep it at 0.11.* for M11, and when Kotlin releases, bump to 1.0?

[MarioAriasC]

The most reasonable solution is to use kotlin versions, so 0.11 for this release and so on

[cy6erGn0m]

@MarioAriasC @benjchristensen So do you have idea when could it be released?

[benjchristensen]

A release can go whenever wanted. @MarioAriasC should have the ability already. Just let me know if there is something not working or needing guidance if it is unclear.

Anyone with commit privileges can tag the branch and it will trigger a build and release. The version for the file and Maven Central is the Git tag name.

[MarioAriasC]

@benjchristensen If we want to use Kotlin versions, in this case 0.11 or M11, 0.11 will be considered and older version compared to 0.21.0? Better if we use M11?

Thanks

[cy6erGn0m]

@MarioAriasC @benjchristensen What about 0.22.11 ?

[MarioAriasC]

@cy6erGn0m @benjchristensen sounds good

[MarioAriasC]

I create this release https://github.com/ReactiveX/RxKotlin/releases/tag/v0.22.11
I don't know if I made it right.

@benjchristensen Could you confirm me?

[cy6erGn0m]

@MarioAriasC @benjchristensen It doesn't work: no release actually done

[orangy]

I wonder if we can speed things up a little bit. If you don't have time/priority for releasing compatible Kotlin bindings for Rx, is it possible we can do it?

[benjchristensen]

You can look at the build information on Travis to see the issue. It failed with a branch config issue.

https://travis-ci.org/ReactiveX/RxKotlin/builds/64004943

Trying to resolve.

[benjchristensen]

I added the necessary config to build.gradle and now the release works fine the way you did it. I deleted and re-added the tag to release.

Build: https://travis-ci.org/ReactiveX/RxKotlin/builds/65133450
Bintray: https://bintray.com/reactivex/RxJava/RxKotlin/0.22.11/view
Maven Sync: https://bintray.com/reactivex/RxJava/RxKotlin/0.22.11/view#central

[MarioAriasC]

Done