Hi all,

To workaround the patch list management, I forked the working project to my private account in github.

And we will work on it verify the patch, then submit code review in gerrit.

So branch should be not needed now.

Best Regards

Shuicheng

From: Xie, Cindy [mailto:cindy.xie@intel.com]
Sent: Tuesday, August 14, 2018 2:46 PM
To: Xie, Cindy <cindy.xie@intel.com>; starlingx-discuss@lists.starlingx.io
Subject: Re: [Starlingx-discuss] patches for SRPM upgrade to CentOS 7.5

Dean,

What is your recommendation for creating a feature branch for CentOS 7.5 upgrade? Right now, as the work is going to have many patches generated, and they have dependencies, it’d difficult to maintain each patches in the mainline with multiple engineers working on the same mainline without actually merge them.

Please advise if you can create the feature branch or you can grant Shuicheng to create it? Then the code review can happen in feature branch and we will generate a build from feature branch for Ada for validation. The merge back to mainline can be done after all sRPM update and test passed with accelerated CR+2 path.

Thanks. - cindy

From: Xie, Cindy [mailto:cindy.xie@intel.com]
Sent: Tuesday, August 14, 2018 1:13 PM
To: starlingx-discuss@lists.starlingx.io
Subject: [Starlingx-discuss] patches for SRPM upgrade to CentOS 7.5

All,

Shuicheng has one story with many tasks open for SRPM (and its dependent RPM) upgrade to CentOS 7.5: https://storyboard.openstack.org/#!/story/2003389

Please provide your code review feedback actively (CR+1, CR+2). However, please hold to have W+1 at this moment. We will do a test build when all 47 sRPM upgrade has been done and mirror upgrade to 7.5 done.

@Ada, please can you kindly support the validation for the build when we are ready?

Thanks. - cindy