For question 1, I think typically the tactic for dealing with upstream fixes is - we source the solution upstream ( in this case, it looks like a solution already exists) - we apply that patch in our repo (example: https://opendev.org/starlingx/upstream/commit/c4bed237e9d60f1bd1cc68400e5548... ) - once we rebase to a newer version of that upstream component, we remove the local patches that already exist upstream. If all of our local patches are no longer needed, and we no longer need to build src rpms, we may switch to prebuilt rpms. - rebasing to a newer version of a component is typically driven by a story, since there can be complications and oftentimes these need to be synchronized For question 2 the openstack upstream projects are locked down through the branch in the manifest (default.xml) Not all are locked down in manifest, but that’s mostly because I'm still cleaning them out (as things are becoming containerized they do not need to be checked out into the workspace) We also include upstream components through lst files in https://opendev.org/starlingx/tools/src/branch/master/centos-mirror-tools Sometimes we need to update these, depending on the problem we are trying to fix. Al -----Original Message----- From: Hu, Yong [mailto:yong.hu@intel.com] Sent: Tuesday, June 04, 2019 1:44 AM To: starlingx-discuss@lists.starlingx.io Subject: [Starlingx-discuss] about openstack-helm version Currently in "~/stx-upstream/openstack/openstack-helm/centos/build_srpm.data", we are using openstack-helm at commit ID "6c71637222f47d85681038994f02feac92f75bd2". However, after "6c716372", there were some fixes for issues we reported, such as, https://bugs.launchpad.net/starlingx/+bug/1829793 so, here come questions: 1. what is the tactic to sync up or update this kind of upstream project? 2. for stx.2.0, have we decided that we lock down the versions of openstack upstream projects? Regards, Yong _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss