v2.3.0 realese

[guolinke]

@StrikerRUS @Laurae2 @jameslamb @henry0312
Which PRs should be included in this release ?

[StrikerRUS]

@guolinke Yeah, just wanted to create an issue about new release. You're reading my thoughts! 😄

I'd like to include:

• Bug fix for first_metric_only on earlystopping #2127 as a bug fix,
• [python] added plot_split_value_histogram function #2043 as a visual addition for a new feature [python] added get_split_value_histogram method #2041,
• Fix build of GPU debugging code #2071 as a bug fix,
• [ci][SWIG] fixed SWIG -Wstrict-aliasing warnings #2139 for "clean" JAR artifact generation.

Also it's will be cool to fix issue

• fix cpp lint problems #1990

before new release.

P.S. Please check recent messages in Slack channel.

[jameslamb]

LGTM. I have nothing to add for this release beyond what @StrikerRUS has noted

[Laurae2]

@guolinke We can also include #2159 in 2.2.4 as it fixes a major bug in the best score returned by the LightGBM booster.

• [R-package] Fix best_iter and best_score #2159 [R-package] Fix best_iter and best_score

[chivee]

adding a reference to #2190.

[StrikerRUS]

I think we have a lot of new features, behavior changes, etc. to label new release as 2.3.0. WDYT guys?

[guolinke]

@StrikerRUS sure, could you make the change?

[StrikerRUS]

Also, I'd like to merge

• Improved python tree plots #2304

before the release. It's ready and awaiting second reviewer.

[StrikerRUS]

I guess the main reason of such long delay #2209 is almost ready. Can we try to review and merge the following PRs before new release as well?

• [examples] Update example notebook #2391 (as default value, which affects only appearance, changer)
• [python] avoid data copy where possible #2383 (as memory saver)
• update feature_fraction_bynode #2381 (as continuation of work on new unreleased feature)
• Predefined bin thresholds #2325 (as new feature)
• code refactoring: cost effective gradient boosting #2407 (as performance improvement)
• [python] make dump_text() private #2434 (as unreleased API changes)

[jayantsahewal]

Is there a tentative target date for this release? There are a few critical bugs which have been fixed and merged in master months ago but haven't been released yet.

[guolinke]

@jayantsahewal sorry, we will move fast for the rest PRs.
@StrikerRUS let us target it before 1 OCT?

[StrikerRUS]

@guolinke Sure! Let's try!

Please don't forget to add a Git tag v2.3.0 in order to trigger changelog generation:

LightGBM/.vsts-ci.yml

Lines 170 to 172 in 7b2963d

	- task: GitHubRelease@0
	displayName: 'Create GitHub Release'
	condition: and(succeeded(), startsWith(variables['Build.SourceBranch'], 'refs/tags/v'))

[StrikerRUS]

Wow, all blocking PRs have been merged! 🎉

[guolinke]

I will create a release soon.

[jayantsahewal]

You guys rock! Thank you so much for getting this release out!!

[StrikerRUS]

@jayantsahewal Thank you and all users for your patience! We are very sorry about the long delay with this release.

[StrikerRUS]

@ankane Sorry for bothering you! Can you please help us to bump the version of LightGBM in Homebrew for the first time? Their docs say that brew should be used for that. But what if I have no macOS? Can I simply edit url and sha256 fields manually?

[ankane]

@StrikerRUS You can edit it manually and submit a PR. The brew command is just a shortcut for it.

[ankane]

Example PR: https://github.com/Homebrew/homebrew-core/pull/44644/files

[StrikerRUS]

@ankane Thanks! I've created: Homebrew/homebrew-core#44685.

[ankane]

Looks great. I think something is wrong with the Homebrew build system (some PRs haven't been built from 5 days ago), so there may be some delay.

[chris-smith-zocdoc]

Should there have been a corresponding java release (lightgbmlib) with this @guolinke ? The latest I see on maven.org is 2.2.400 from August https://search.maven.org/search?q=g:com.microsoft.ml.lightgbm

[StrikerRUS]

@chris-smith-zocdoc We released JAR files here in our repo: https://github.com/microsoft/LightGBM/releases/tag/v2.3.0. For maven update, ping @imatiach-msft .