I was working on version 2.1 on centos 6.5. with the release of version 2.2 I have been testing the upgrade path of gluu-server. I have noticed that after importing the rpm repositories and rpm key running yum update gluu-server correctly notices that there is an update between the two. Running the update does not correctly determine if gluu-server is currently running and will produce an interesting error condition if gluu-server was not previously stopped. basically version 2.1 was still running and not successfully removed but all of the init.d scripts were switched over so I had to manually remove and stop it. If gluu-server was stopped it successfully removed 2.1 and installed 2.2, however no user data was transferred over. This will not work in a production environment with users already in the system. My request is that for the upgrade path at the very least users and passwords are transferred over with running yum update gluu-server