![]() That's written in the docs on the link you gave, Is the move from 3.x to 3.y considered a major or minor update? Or is major version always the first number? In addition to answering to above question, the terminology of major and minor updates should be clearly visible. I agree with you for the documentation though. This aims to clean up the code, since upgrades jumping 2 major versions are too risky and hard to maintain, we'll keep only migration from that last major (in this case 3.x). To update to version 4.0.0 you'll need to be running at least version 3.0.0, otherwise you might loose some database migrations which might have unexpected effects. In the changelog of 4.0.0, they wrote the following: I upgraded from 3.18.2 to 4.1.2 without problems. Information is not available, of it it is there, it is hard to find Server Setup Information: Information is easily available Actual behavior: Try to find out what is the safe upgrade path from RC 3.18.3 to RC 4.1.2.Is the move from 3.x to 3.y considered a major or minor update? Or is major version always the first number? Steps to reproduce: Otherwise the functionality may break in unexpected ways.įor example now when we'd like to move from 3.18.3 to 4.1.2, can 4.0.6 be skipped safely? Since different versions include changes to database schema, it is important that one does not skip too many versions of RC when upgrading from LTS versions to the latest available version. Https:///getting-support#rocket.chat-versions contains the latest and supported versions.īut so far we haven't been able to find any official word on the minor versions of RC that can be safely skipped at.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |