Quote:
Originally Posted by _dave_
Remember back a few weeks, the early 4.11 updates failed at this simple task, producing backups that were useless to 4.10.x. I am unsure if this is corrected in the latest 4.11 release.
Imo as a tool for serious players, you should strongly reconsider this approach of releasing versions with at best a month or two of support. Look at a company like Microsoft - they didn't stop supporting or releasing updates to windows XP the day Vista was on sale, instead it was supported and updated until only a few weeks ago! and still is for corperate customers.
Anyone who plays semi-seriously should be extremely wary of updating anything. Like a corporate IT department - they don't just rush to install any and every update the developers publish, they test and test and test. Many companies won't even have had a full rollout of Windows 7 yet, although almost all will be looking at it.
PT should decouple feature updates from bugfixes. There is no reason why 4.10.6 user should have to suffer the horrors of an experimental custom cache implementation, if they have no need for it and simply want PT4 to keep producing a HUD on their tables.
Data was
NOT damaged during the 4.11 upgrade process, your post may accidentally confuse the issue for users who are not as experienced as you are.
(note - _dave_ is a very advanced PT4 user, and is typically a trusted source of knowledge about PT4 but in this situation his post was not related to the fear the user had about risking data loss).
Data was safe and secure at all times, we have no records of any users whose data was destroyed by the 4.11 upgrade process.
During the 4.11 upgrade process some users chose to re-import and create a new database, this was not required but it was a wise choice if they wished to have many of the latest improvements that were only available during a fresh import. Some other users experienced issues related to antiquated versions of PostgreSQL, some of these users had the option of installing a new version of PostgreSQL, backing up, and then restoring their database - OR - create a new database and import their existing hands which were safely stored to once again take advantage of import improvements while at the same time upgrading to the new PostgreSQL version. These were both optional choices, but they were not mandated nor did they risk any data.
- TT