There is a change in behavior from ZMF 7.1.3 to 8.1.1 with regard to ERO and the Demotion functionality. If you have package A connected to R1. Then promote it to SITE1, a release promotion site. Afterwards, it was promoted to SITE8, which is NOT a release promotion site.
If USERA attempts to edit a component that was previously saved by USERB, the changes are not saved and "Checkin failed CMN8262I - Component to be staged is locked by USERB." is issued. Also, Admins are allowed to edit the component successfully. If the user logins to ISPF ZMF, saves the component there and then attempt the edit in ZMF for Eclipse, the edit is then successful.
When a component is XML checked into a package where it already exists any changes to the user options (&USROPnn) for that component in that package are lost.
When components are being edited they are not marked INCOMP until the changes are saved/the user leaves the edit session. However, the possibility exists that one user may be actively editing a component whilst another user is in the process of baselining a package. In this situation, the user who is editing the component can still complete their changes and re-build the component in the package datasets despite the fact that the installation process is underway or the package has already been baselined.
