Hi Eli, On 03/13/2013 03:41 PM, Eli Mesika wrote:
On 03/11/2013 03:17 PM, Eli Mesika wrote:
Please make sure to upgrade to latest 3.1.z before upgrading to 3.2
Would you mind explaining why? It's funny that I would need to upgrade in 2 steps: Update 3.1 to tip of branch, then upgrade to 3.2.
Were there any database schema changes withing the 3.1.* releases?
There we some bugs that were related only to 3.1 and therefore fixed only on the 3.1 repository. I had consulted on that with Barak and I have been told that it is OK to ask to upgrade to latest 3.1.z before upgrading to 3.2 If this is wrong from your POV, please open a discussion on engine-devel and I will be glad to follow any new directions requested by the community.
Of course it's OK to ask :-) I think it's OK to ask why, also. I'm just wondering if there is some reason why an upgrade might work better from 3.1 branch tim than from the 3.1 release (or 3.1.1 if there was one, but I don't remember it). Thanks! Dave. -- Dave Neary - Community Action and Impact Open Source and Standards, Red Hat - http://community.redhat.com Ph: +33 9 50 71 55 62 / Cell: +33 6 77 01 92 13