Releasing 1.1.0

[abersnaze]

I would like to share what out plans are for 1.1.0. At the moment we've built up quite a lot of @Experimental APIs that we would like more confidence in using long term in production. To that end we would like to promote them to express that they are stable. I've captured some consensus among the core committers about what APIs we would like the promote. Because it wasn't entirely unanimous this is what I plan to do:

• Last call for merges before publishing 1.0.15 for the next two weeks. Our goal is to only have changes to the annotations between the last patch and 1.1.0 so that they are functionally equivalent.
• Submit PRs to change the annotations on various APIs but not merge them.
• Discus the various merits of the PRs.
• Publish 1.0.15.
• Merge the annotation change PRs that we can agree on (minimum of 3 👍 or three weeks which ever is first).
• Publish 1.1.0.

[akarnokd]

👍 sounds great.

Submit PRs to change the annotations on various APIs but not merge them.

I'd like to add that Observable hosts quite a set of the proposed APIs and may become difficult to have non-conflicting PRs targeting this single class, if said PRs are per functionality and not per class.

[DavidMGross]

Please don't forget to update the "@SInCE" javadoc annotations as well if
you remove the @Experimental/@beta annotations as you promote any APIs.
You can set @SInCE to simply the string "1.1.0"

On Fri, Sep 25, 2015 at 12:45 PM, George Campbell notifications@github.com
wrote:

I would like to share what out plans are for 1.1.0. At the moment we've
built up a quite a lot of @experimental APIs that we would like more
confidence in using long term in production. To that end we would like to
promote them to express that they are stable. I've captured some consensus
among the core committers about what APIs we would like the promote. It
wasn't entirely unanimous and this is what I'm planning to do.

• Last call for merges before publishing a 1.0.15 for the next two
  weeks. Our goal is to only have changes to the annotations between the last
  patch and 1.1.0; so that they are functionally equivalent.
• Submit PRs to change the annotations on various APIs but not merge
  them.
• Discus the various merits of the PRs.
• Publish 1.0.15.
• Merge the annotation change PRs that we can agree on (minimum of 3 [image:
  👍] or three weeks which ever is first).
• Publish 1.1.0.

—
Reply to this email directly or view it on GitHub
#3378.

David M. Gross
PLP Consulting

[abersnaze]

@akarnokd I have faith in git's abilities to handle mutually exclusive changes in the same file.

[abersnaze]

@DavidMGross thanks for the reminder.

[akarnokd]

Submit PRs to change the annotations on various APIs but not merge them.

To be clear, will you @abersnaze port these PRs or should this task be shared among us all?

[abersnaze]

I've got a spreadsheet that I've collected the feed back in. I was planning on submitting most these PRs.

[akarnokd]

If you don't mind, I'll handle the cases which I proposed, especially if it involves removing a feature because the dependencies have to be cleared up as well.

[akarnokd]

Never mind, I've done all PRs, although grouped by function instead of the grouping in the spreadsheet.

[abersnaze]

Last call for pull requests to be merged for 1.0.15. I'm trying to recruit @stevegury and @stealthcode to help review #3169 and #3150.

[stealthcode]

@akarnokd @abersnaze the public api promotion changes all have the javadoc annotation @since 1.0.15. I thought the promotions were going to be accepted after 1.0.15 but before 1.1.0. In that case shouldn't the annotations say 1.1.0?

[abersnaze]

All the tasks were done.