Closed adrian-wozniak closed 6 years ago
Can you rebase and describe your changes?
@dstepanov Changes are at the top of master, I'll not squash them, cause I think reviewing commit by commit gives you possibility to focus on one change and see only code changes required by particular version updates. Some more details added as a comments near key changes.
Please squash your change so we have nice git log
Sorry, but I'll not squash those commits. I want to have every version change separated to easily see why some code changes were done and actually this is how changes are committed to this repository. I really don't understand why you force me to do that. "Nice git log" is an argument that doesn't convince me, cause it has to be useful.
Well I guess it makes sense, I haven't seen PRs with 27 commits
You can have PR with 100 commits... it's not a crime :). It's very valuable to see the way how whole change was created. It's easier to understand it. With squash you loose that ability, but if you want to see change as a whole than with small commits you're still able to do that.
I know people who have commit for every change in their code ;) Bumping lib version
is enough for me.
It's good to have newest versions of used libraries...
This PR update versions of almost all used 3rd parties.
The most important is Spring Cloud Edgware.RELEASE.