True, we will want to wait if we want decide to move or copy the rackerlabs/craton repo. I can create the project patch and then pin it so it doesn't get merged.
On Wed, May 25, 2016 at 10:27 AM, Jim Baker <jim.ba...@python.org> wrote: > Sean, thanks for your help here, it's very much appreciated! > > The move then should be straightforward once we get past our first > milestone, on or around June 10; but any prep in advance sounds good. > > > > On Wed, May 25, 2016 at 12:37 PM, sean roberts <seanrobert...@gmail.com> > wrote: > >> Now that we have settled on the name, setting up the project >> infrastructure is straightforward. I have done this a few times and am >> ready to do it for craton. >> >> On Tue, May 24, 2016 at 3:51 PM, Jim Baker <jim.ba...@python.org> wrote: >> >>> On Tue, May 24, 2016 at 6:36 PM, Sam Morrison <sorri...@gmail.com> >>> wrote: >>> >>>> I’m in favour of using 3.5. We are in the process of moving things to >>>> ubuntu xenial and 3.5 is native there. >>>> >>> >>> Thanks for the feedback! >>> >>> >>>> >>>> BTW when is Craton planning on getting into openstack gerrit etc? >>>> >>> >>> The specific timeline of the move to gerrit is not something we have >>> actively discussed, because of the usual: we are trying to complete our >>> phase 1 milestone. Currently we are projecting June 10 (based on Monte >>> Carlo modeling), but this could slip. In any event, once we finish >>> milestone 1, moving to OpenStack Gerrit and infrastructure in general ASAP >>> would make sense. >>> >>> In other words, it should be quite soon! >>> >>> - Jim >>> >>> _______________________________________________ >>> OpenStack-operators mailing list >>> OpenStack-operators@lists.openstack.org >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators >>> >>> >> >> >> -- >> >> ~ sean >> > > -- ~ sean
_______________________________________________ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
