Merge lp:~thomas-voss/process-cpp/empty-mp-for-landing into lp:process-cpp

Proposed by Thomas Voß
Status: Merged
Merge reported by: Michal Hruby
Merged at revision: not available
Proposed branch: lp:~thomas-voss/process-cpp/empty-mp-for-landing
Merge into: lp:process-cpp
Diff against target: 0 lines
To merge this branch: bzr merge lp:~thomas-voss/process-cpp/empty-mp-for-landing
Reviewer Review Type Date Requested Status
Michael Zanetti (community) Approve
PS Jenkins bot continuous-integration Approve
Review via email: mp+206355@code.launchpad.net

Commit message

Empty MP to sync trunk with image.

Description of the change

Empty MP to sync trunk with image.

* Is your branch in sync with latest trunk (e.g. bzr pull lp:trunk -> no changes) - Yes
* Did you build your software in a clean sbuild/pbuilder chroot or ppa? - Yes
* Has your component "TestPlan” been executed successfully on emulator, N4? - No per component test plan, executed the Unity8 one.
* Has a 5 minute exploratory testing run been executed on N4? - Yes
* If you changed the packaging (debian), did you subscribe a core-dev to this MP? N/A
* If you changed the UI, did you subscribe the design-reviewers to this MP? N/A
* What components might get impacted by your changes? unity-mir/unity8
* Have you requested review by the teams of these owning components? Not yet.

To post a comment you must log in.
Revision history for this message
PS Jenkins bot (ps-jenkins) wrote :
review: Approve (continuous-integration)
Revision history for this message
Michael Zanetti (mzanetti) wrote :

 * Did you perform an exploratory manual test run of the code change and any related functionality?

Not sure tbh. But it seems this "change" shouldn't do any harm. The releasing of the package however, needs to be tested when the package is in the silo.

 * Did CI run pass? If not, please explain why.

seems so...

review: Approve

Preview Diff

Empty

Subscribers

People subscribed via source and target branches