-
I updated from 5.1 to 5.2.1 recently. Unfortunately #3769 is part of the 5.3 milestone, so it's not live yet. Problem is that there were a bunch of breaking changes related to static value converters in 5.2 that I've already made corrections for and I was hoping I didn't have to roll back those changes as well. I was wondering if it's possible for me to somehow update to a pre-release on my own? Or maybe I should clone/build the repository and reference it directly until 5.3 is released? What would you guys consider good practice in this scenario? |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments
-
@jbooth88 I'm quite certain there is no difference in the quality between a prerelease and a non-prerelease version. Every merge to the main branch has to pass the tests, and for a "full" release no further tests are performed. |
Beta Was this translation helpful? Give feedback.
-
Last time I checked I couldn't find any prerelease builds. Now I found a 5.2.2 prerelease. Weird. |
Beta Was this translation helpful? Give feedback.
-
@corvinsz is correct, there is virtually no difference between the nightly pre-release builds and the full builds. The only difference is I tend to make a final pass with the demo app before kicking a full release build, but other than that, the quality level should be identical. |
Beta Was this translation helpful? Give feedback.
@jbooth88 I'm quite certain there is no difference in the quality between a prerelease and a non-prerelease version. Every merge to the main branch has to pass the tests, and for a "full" release no further tests are performed.
You should be fine using a prerelease, though I would recommend to upgrade to the latest full release once that is out.