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

bump version #3344

Merged
merged 5 commits into from
Sep 2, 2020
Merged

bump version #3344

merged 5 commits into from
Sep 2, 2020

Conversation

guolinke
Copy link
Collaborator

@guolinke guolinke commented Sep 1, 2020

No description provided.

@guolinke
Copy link
Collaborator Author

guolinke commented Sep 1, 2020

@jameslamb could you update R's version accordingly? you can create a new PR if needed.

@jameslamb
Copy link
Collaborator

We don't necessarily know that the next release will be 3.0.1 instead of 3.1.0, right?

What do you think about the convention where the development version is like 3.0.0.9999 (newer than 3.0.0, older than any future release we do with a 3-part number), and then we change to 3.0.1 or 3.1.0 based on what is new?

If any new features are added between now and the next release, then that release should be 3.1.0. If it is only maintenance tasks, 3.0.1

@guolinke
Copy link
Collaborator Author

guolinke commented Sep 1, 2020

I like the proposal. With that, we can distinguish the dev and release versions.

.appveyor.yml Outdated Show resolved Hide resolved
VERSION.txt Outdated Show resolved Hide resolved
@guolinke
Copy link
Collaborator Author

guolinke commented Sep 1, 2020

After merge this, we can start to merge the blocked PRs about new features.

@jameslamb
Copy link
Collaborator

I'll update the R version right now and make a PR into this one

@jameslamb
Copy link
Collaborator

I can also upload the R artifacts to the 3.0.0 release manually tonight

@jameslamb
Copy link
Collaborator

created #3345

@guolinke guolinke merged commit 8fc80bb into master Sep 2, 2020
@StrikerRUS StrikerRUS deleted the bump-ver branch September 2, 2020 10:45
@github-actions
Copy link

This pull request has been automatically locked since there has not been any recent activity since it was closed. To start a new related discussion, open a new issue at https://github.com/microsoft/LightGBM/issues including a reference to this.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 24, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants