For backporting a fix to r/2018.10, I've got a repo setup on that branch and cherry-picked the change, and I'm building a load to test while waiting for Zuul to process the update to master. Maybe a stupid question, but do I need to change the "Change-Id" for the commit (ie. delete it and amend the commit) to avoid collision with the original when I create the new gerrit review? -----Original Message----- From: Jones, Bruce E [mailto:bruce.e.jones@intel.com] Sent: Monday, October 01, 2018 1:14 PM To: Dean Troyer; starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] r/2018.10 branch merges complete Dean, thank you! I'm looking forward to seeing posts to the mailing list of successful builds on the branch, hint hint :) brucej -----Original Message----- From: Dean Troyer [mailto:dtroyer@gmail.com] Sent: Monday, October 1, 2018 10:02 AM To: starlingx-discuss@lists.starlingx.io Subject: [Starlingx-discuss] r/2018.10 branch merges complete It looks like the last of the 'setup' reviews for the r/2018.10 branch merged a few hours ago, thank you to those who reviewed those. This means that a) master is open again for ongoing work b) we are ready to do release branch builds directly from Gerrit via stx-manifest (check out r/2018.10 and use that default.xml) Don't forge that bug fixes should merge in master before being backported to r/2018.10. dt -- Dean Troyer dtroyer@gmail.com _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss