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

update vue to version 2.5.22 #96

Closed
wants to merge 1 commit into from
Closed

Conversation

garnet420
Copy link
Collaborator

No description provided.

@Razenpok
Copy link
Collaborator

I actually want to wait until 2.6.0 - it's almost out: https://github.com/vuejs/vue/projects/4
The main reason for waiting for 2.6.0 and not upgrading to 2.5.22 now is that I don't really want to do regression testing twice, as version upgrade is a rather major change.
The main reason for 2.6.0 instead of 2.5.22 is that it will improve TimeSpan integration in template, allowing to omit .toString() calls: vuejs/vue#8093

@Razenpok Razenpok closed this Jan 16, 2019
@Razenpok
Copy link
Collaborator

Feel free to remove the branch

@garnet420
Copy link
Collaborator Author

If this is the approach, what are you going to do when 2.6.1 comes out?

@Razenpok
Copy link
Collaborator

Depends on what it brings to the table; we will skip it if we won't benefit from the update. If it does have something useful, then it depends; if it has some critical stuff - we will update to 2.6.1 right away; if it has only minor improvements, we will check what will be in 2.6.2 - if nothing, we will update to 2.6.1 right away, otherwise wait for 2.6.2.

@garnet420
Copy link
Collaborator Author

2.6.1 is going to be a buxfix release. If you at, for example, 2.5.18 (which had some features), everything after that (really, including 2.5.22) was bugfixes. Some of the most common bugs that vue tends to have, given the release history, are memory leaks. Not something that we have been trying to catch.

2.6 is going to inherit all of 2.5.22's features and fixes. So, in all likelihood, any regressions from switching to 2.5.22 will show up in 2.6.0.

I am not even sure what you mean by regression testing. It's not like we have a separate GUI test process. People just point out glitches as they see them.

Handwringing about tracking third party libraries is how people end up with broken versions of SSL.

@garnet420 garnet420 reopened this Jan 16, 2019
@Razenpok Razenpok closed this Jan 16, 2019
@Razenpok Razenpok deleted the update_vue_version branch January 22, 2019 18:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants