On 05/19/2017 07:28 AM, Robert Varga wrote: > On 18/05/17 16:11, Andrew Grimberg wrote: >> So, my intent with the auto-close is to have Gerrit clean-up a bunch of >> the open changes so that when we do start the migration then we're far >> more likely to be able to get a good idea of who we're going to have to >> talk to to get things reconnected and user names fixed where needed. > > Right, but that really has nothing to do with abandoned patches, lest > you are proposing to not migrate them. > > The reason for it being that even abandoned patches have an owner, which > presumably needs to map to an identity due to the obvious question: who > will be the owner if the patch is ressurrected?
The way the import tool works is that it auto-creates accounts in the target Gerrit system if they don't already exist. If the account has a backing account already existing in the new backend LDAP then the account is created as an enabled account, if it doesn't, then it is created as a disabled account. We want to reduce the problem set of likely responsive people so that we can get the accounts linked back up to what they need to be must faster as the intent would be to check to see who the owners of still open changes are and if they got created as disabled accounts to reach out and coordinate getting the LFID properly attached, which may mean changing their Gerrit username or it may just mean that they need to create their LFID with the same name and we re-enable their account. As for the owner of a resurrected path, the owner may still be the same, but whoever uploads / re-opens the change becomes the last submitter of record. -Andy- -- Andrew J Grimberg Lead, IT Release Engineering The Linux Foundation
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Discuss mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/discuss
