On 18/05/2015 18:29, John Spray wrote:> > > On 18/05/2015 09:09, Loic Dachary wrote: >> One problem with promoting http://github.com/ceph/ceph to that role is that while the migration is in progress there will be two queues of pull requests, the new one at http://github.com/ceph-ci/ceph and the old one at http://github.com/ceph/ceph. Given our current flow of pull requests the migration will probably take about three months. And after that, since it's not possible to forbid pull requests on github.com (you can disable issues but not pull requests on a given repository) there will forever be a flow of misdirected pull requests against the old repository. > If I understand correctly, this is not an issue as pull requests would still be against the original ceph repository. The ceph-ci repository would be where people could push their branches directly to have them built, and then they could create a PR to the ceph repository (either from their branch on ceph-ci or their original branch in their own github repo). > > So my workflow as a developer would be to write some code locally, push my branch to /jcsp/ceph to "save" it, push it to /ceph/ceph-ci to have the gitbuilders pick it up and build it, and then ultimately make a PR to /ceph/ceph to merge it. > > Apologies in advance for muddying the water if I've got any of that wrong :-) I think you got it right, I misunderstood the original proposal. +1 on the original proposal then. It's less work than having a ceph-release repository. Sorry for the noise :-) > > Cheers, > John -- Loïc Dachary, Artisan Logiciel Libre
Attachment:
signature.asc
Description: OpenPGP digital signature
