Originally posted by Brane215
View Post
Now consider this if you want to change from version 5.1.3 to a version 5.1.4, on a project you know after years of using their product they take regressions seriously and only fix those (in a rather carfeul way not to break anything) in minor point releases. Its something you can setup as general rule that such minor point releases are worthy candidates to checkout and spend time testing.
If its just release 2014.7 or whatever they call it then you can start digging through changelogs and weighting the improvements vs risks before even considering talking to some project leader who has no deep knowledge compared to more specialized personal but has to make the decisions. Its something rather hard to put in a guideline, if the project itself bases its version on PR (bigger = better) than being more "open and directy" about compatibility and type of changes.
I doubt anyone still argues that Firefox and Chrome Numbering scheme has any other use than display how useless it is.
Comment