The Wayback Machine - https://web.archive.org/web/20220317132408/https://github.com/microsoft/LightGBM/issues/3763
Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

List of dependencies that should be updated from time to time #3763

Open
StrikerRUS opened this issue Jan 14, 2021 · 6 comments
Open

List of dependencies that should be updated from time to time #3763

StrikerRUS opened this issue Jan 14, 2021 · 6 comments

Comments

@StrikerRUS
Copy link
Collaborator

@StrikerRUS StrikerRUS commented Jan 14, 2021

Here is a list of different places in LightGBM's GitHub repo where we specify some dependencies or helpers. Quite often we should specify a particular version of such software. And these versions are tend to obsolete with time. If you see that there is a newer version comparing to what we have, please feel free to propose a PR with updates or simply leave a comment here.

@StrikerRUS
Copy link
Collaborator Author

@StrikerRUS StrikerRUS commented Jan 16, 2021

@jameslamb Please help to clarify. Should we monitor new releases for R 3.x stuff or they have been frozen forever?

@jameslamb
Copy link
Collaborator

@jameslamb jameslamb commented Jan 16, 2021

@jameslamb Please help to clarify. Should we monitor new releases for R 3.x stuff or they have been frozen forever?

No R 3.x resources will change.

Rtools for R 3.x is frozen forever. https://cran.r-project.org/bin/windows/Rtools/history.html

image

We also do not need to look for new versions of R itself. R doesn't have a concept of "long-term support" releases like other projects. So you won't see a bugfix that results in, say, R 4.1.1 and R 3.6.4 at the same time.

You can see the history of release dates at https://cran.r-project.org/bin/windows/base/old/.

@StrikerRUS
Copy link
Collaborator Author

@StrikerRUS StrikerRUS commented Jan 16, 2021

I'm so sorry for my English, but I can read this answer in two ways. Which one is correct? 😄

No, R 3.x resources will change.

No R 3.x resources will change.


Rtools for R 3.x is frozen forever.

Ah, I see, thanks! Removed from the list.

You can see the history of release dates at https://cran.r-project.org/bin/windows/base/old/.

I see there are

R 4.0.3 (October, 2020)
R 4.0.2 (June, 2020)
R 4.0.1 (June, 2020)
R 4.0.0 (April, 2020)

What about 4.0.4? Why we shouldn't wait for it?

@jameslamb
Copy link
Collaborator

@jameslamb jameslamb commented Jan 16, 2021

Oh sorry, let me rephrase.

  • there will never be a new R 3.x release
  • there will never be a new Rtools 3.x release

For 4.x series, there will continue to be new releases. They tend to do 4 or 5 per year. The next release of R will be R 4.1.0. That might or might not involve a new Rtools 4.x release. I use this mirror of the R source (R development is not actually done on GitHub) to keep track: https://github.com/wch/r-source/blob/trunk/VERSION

@StrikerRUS
Copy link
Collaborator Author

@StrikerRUS StrikerRUS commented Jan 16, 2021

Thank you very much!
Then I'm removing R 3.x from the list as well.

The next release of R will be R 4.1.0. That might or might not involve a new Rtools 4.x release.

Got it, great! Then I think we can have them both in the list.

They tend to do 4 or 5 per year.

Quite frequent. For instance,

Visual Studio version for OpenCL libraries integration

VS releases have 2-year cycle, but I still find it useful to have VS mentioned here.

@jameslamb
Copy link
Collaborator

@jameslamb jameslamb commented Apr 18, 2021

I want to note here that R 4.1.0 is planned for release on May 18, 2021.

https://twitter.com/pdalgd/status/1383008275545919488

You can see a full list of changes in that version at https://stat.ethz.ch/R-manual/R-devel/doc/html/NEWS.html. There is only one that looks immediately relevant to {lightgbm}, although it's hard to tell since some of the changes are deep in the internals of R and {lightgbm} may indirectly rely on them.

The default C++ standard has been changed to C++14 where available (which it is on all currently checked platforms): if not (as before) C++11 is used if available otherwise C++ is not supported.

Packages which specify C++11 will still be installed using C++11.

Either specify C++11 (see ‘Writing R Extensions’) or modernize the code and if needed specify C++14

I don't think {lightgbm} needs to worry about this, because it already declares its use of C++11 in the way that is recommended by "Writing R Extensions"

I don't think that any action is required at this time to prepare for R 4.1.0. But that release will be a big one so I just wanted to note that it's coming so we're prepared.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
2 participants