Archive this repo?

[jsignell]

Since the functionality has been moved to xgboost itself. Would now be the appropriate time to archive this repo?

[jrbourbeau]

cc @TomAugspurger @mmccarty @gforsyth

[gforsyth]

We've moved our work over to xgboost.dask, so for our purposes, anyway, this repo can be archived.

[jakirkham]

SGTM. Should we update the README to reflect this?

[jrbourbeau]

That sounds good. Similar to dask-lightgbm, we might also consider issuing a final release before archiving which adds a warning that the functionality in dask-xgboost has been moved into xgboost and dask-xgboost is no longer maintained

[jakirkham]

cc @hcho3 @trivialfis @JohnZed (for vis)

[trivialfis]

Can we wait for xgb 1.4? I would like to get the integrated version feature complete at this version.

[TomAugspurger]

Adding a warning, updating the docs, and archiving sounds good to me.

…

On Feb 8, 2021, at 5:58 PM, Jiaming Yuan ***@***.***> wrote: Can we wait for xgb 1.4? I would like to get the integrated version feature complete at this version. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#80 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAKAOISKJADLOBITAKQVL5DS6B3DDANCNFSM4XJUEKWQ>.

[JohnZed]

In the near future, I'd be totally onboard with archiving. But I agree with @trivialfis - there are still a few more minor bits coming for xgboost.dask in 1.4 (DART algo comes to mind?), so archiving this project after 1.4 is out would sound most appealing, as then we can clearly say there is no reason to use it for any new code.

[trivialfis]

Hi, XGBoost 1.4.1 is out and available on pypi. I believe we can safely redirect users to the xgboost.dask module in the future as it's mostly feature-complete now. Thanks for the excellent work everyone! ;-)

[jsignell]

Great! So what's needed is a note on the readme and then for someone to push the "archive button"?

[jrbourbeau]

Adding a promonant note to the README sounds good. I'll propose we also add a warning which points users to xgboost.dask (similar to what we did with dask-lightgbm) and issue a final release.

[jakirkham]

There's also some references to Dask-XGBoost in Dask-ML ( dask/dask-ml#844 ). We may want to remove those as well.

[jrbourbeau]

Just pushed out 0.2.0 which contains deprecation warnings (xref #84). Planning to archive this repo tomorrow morning (in the central time zone)

[jakirkham]

Thanks James! 😄