Re: [Openstack-operators] [craton] Versions of Python to support for Craton
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 wrote: > On Tue, May 24, 2016 at 6:36 PM, Sam Morrison 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 ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] [craton] Versions of Python to support for Craton
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 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 > 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 wrote: >> >>> On Tue, May 24, 2016 at 6:36 PM, Sam Morrison >>> 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
Re: [Openstack-operators] [craton] Versions of Python to support for Craton
I can make the request a move rather than copy. Then anyone landing at the old repo get redirected to the new. On Wed, May 25, 2016 at 10:37 AM, Jim Baker wrote: > We will want to move the main repo to OpenStack infra, with the usual > mirror to github.com/openstack/craton. I don't think we need to worry > about mirroring to github.com/rackerlabs/craton as well. A simple > reference there pointing to the new location should suffice. > > Basically I'm just trying to keep disruption to the dev team to > zero/minimum. > > > On Wed, May 25, 2016 at 1:31 PM, sean roberts > wrote: > >> 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 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 >>> 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 >>>> wrote: >>>> >>>>> On Tue, May 24, 2016 at 6:36 PM, Sam Morrison >>>>> 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 >> > > -- ~ sean ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
