Based on what I noticed so far, the strongest drive for a migration is a new feature coming/ bugfix coming. It's usually the only way to convince the business layer in small/mid size companies not tech oriented.
In general I would say it is quite important to avoid lagging to much behind ( keeping the difference in major version <2 ). Last observation based on experience, never just migrate to the latest/recent version without a deep check of the changelists and community resources. It is quite common that a version 6.x.0 is released and then some regression or bug is discovered and 6.x.1 ( sometimes 6.x.2 is released) . So it always good to investigate the community and changelists to find the minimum (safe) Solr Version . In relation to that, I have actually a concern as there are some "famous" Solr versions affected by bugs. I don't know what happens in those cases but I would like to see those releases impossible to download/install after the bug as been fixed ( I think a recent example was 6.4.0 which has some big regression). Regards ----- --------------- Alessandro Benedetti Search Consultant, R&D Software Engineer, Director Sease Ltd. - www.sease.io -- View this message in context: http://lucene.472066.n3.nabble.com/Version-upgrading-approaches-tp4326976p4326993.html Sent from the Solr - User mailing list archive at Nabble.com.
