Open Stack

On 07/15/2014 11:47 AM, 金子　雄大 wrote:
> Hi Josh,
> 
> Thank you for your help!
> I'll do as you say.
> Should I delete the upstream part of projects.yaml?
> 
> Regards,
> takehiro
No, deleting the upstream url in projects.yaml is not required.

The system acts on that line during project creation only, subsequent
reads of that file do not result in any further activity on the upstream
url.

Thanks takehiro,
Anita.
> 
> (2014/07/15 18:00), Joshua Hesketh wrote:
>> Hi takehiro,
>>
>> The upstream part of projects.yaml is simply for the initial import. After that it is expected that stackforge (either from git.openstack.org or through the stackforge org on github) is the canonical repository. ie, your other upstream is no longer 'upstream' so to speak.
>>
>> My recommendation would be to remove your old upstream and just use the stackforge one. The reason being is that you want all new patches to go through gerrit anyway so there is no real use of another upstream. You could create a fork or mirror on github elsewhere but you do already have the copy in the stackforge org.
>>
>> I hope that helps!
>>
>> Cheers,
>> Josh
>> ________________________________________
>> From: 金子　雄大 [takehiro.kaneko at ctc-g.co.jp]
>> Sent: Tuesday, July 15, 2014 11:59 AM
>> To: openstack-infra at lists.openstack.org
>> Subject: [OpenStack-Infra] develop on upstream or stackforge
>>
>> Hi all.
>>
>> I'm working on a stackforge project "rack".
>> We have an upstream repository on github that is different from
>> stackforge one.
>> I pushed my patch to Gerrit and it was merged to our stackforge github,
>> but the change wasn't merged to upstream github.
>> Should I push my patch to upstream github?
>> And the patch is also merged to stackfoge github?
>>
>> Regards,
>> takehiro
>>
>> _______________________________________________
>> OpenStack-Infra mailing list
>> OpenStack-Infra at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
>>
>