 |
 |
On 03/02/12 13:26, Mario David wrote: > dear Adrian, all > > for clarification of this EMI-UMD issue > > EGI takes EMI MW and submit's it through a process of verification and staged rollout > > UMD is not a repackage or other sort of tampering with the SW coming out of EMI > the verification and staged rollout are tests done with new EMI releases (or updates) > the results of those tests are documented and publicly available > > while verification, tests basic successful installation and configuration of a given component, check the documentation > release notes, and may perform some basic functionality tests > > the staged rollout is primarily done by early adopter sites that deploy the new version in production (or quasi-production) instances > and check it's behavior in production environment and real users and VO's > > it is perceived as a cache before wide deployment or availability to the production infrastructure > > of course we don't aim to catch all problems/issues/bugs, but we aim to lower the probability that such problems arise > before wide deployment. > > the process of verification and staged rollout takes some time, and as such in many cases the versions of the MW available > in the production repos of EMI are newer than in the production repos of UMD. > > kind regards > > Mario David > (EGI TSA1.3) Great! Thanks for explication! So ... UMD is the verified (stable) version of EMI software .. and should i understood that for sites that just want (need or told to) upgrade the UMD is recommended version? Thanks, Adrian