My understanding is that everything in the migration spreadsheet is considered migration work and thus doesn't require PR approvals.
DR No dia 12/07/2014, às 07:09, Guewen Baconnier <[email protected]> escreveu: > > Le 12 juil. 2014 00:37, "Holger Brunn" <[email protected]> a écrit : > > > > Ladies and gentlemen being concerned with the bzr->git migration, > > > > we have a rulebook to do the migration, and a rulebook to handle merge (now: > > pull) requests. The migration guide is not decisive, but most people > > including > > me do the necessary changes as a PR. which stalls a lot of migrations > > because > > either there's not enough thumbs up or thumbs up with nobody to actually > > pull > > the proposal. Wouldn't it make sense to allow the migrator to do > > non-reviewed > > direct merges of the .* files? > > > > -- > > Therp - Maatwerk in open ontwikkeling > > > > Holger Brunn - Ontwerp en implementatie > > > > mail: [email protected] > > web: http://therp.nl > > +1 > Migration is part of the maintainers role and they should be able to proceed > with the migration/maintenance tasks by themselves. This is also a matter of > time. The migration is still running and the more long it will take time the > more it will be painful and difficult to understand for contributors. > > By the way, there are still projects waiting for a maintainer and still > maintainers that did nothing on the migration. Thanks to them to put their > name on a few projects on the migration spreadsheet. > > Cheers > _______________________________________________ > Mailing list: https://launchpad.net/~openerp-community > Post to : [email protected] > Unsubscribe : https://launchpad.net/~openerp-community > More help : https://help.launchpad.net/ListHelp
_______________________________________________ Mailing list: https://launchpad.net/~openerp-community Post to : [email protected] Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp
