View source for OpenEmbedded Merge Policy
From Openmoko
You do not have permission to edit this page, for the following reasons:
You can view and copy the source of this page:
Return to OpenEmbedded Merge Policy.
You do not have permission to edit this page, for the following reasons:
You can view and copy the source of this page:
Return to OpenEmbedded Merge Policy.
What to check when merging upstream OpenEmbedded into the org.openmoko.dev branch.
Make sure that a build from scratch is still working. This is specially interesting when a toolchain upgrade has happened or other major components were changed.
If packages from the task-openmoko-feed are not buildable anymore do not remove them but make them build. If it was removed from OpenEmbedded look at the reason and make a decision.
The upgrade path is important to us. Make sure that version numbers do not jump backwards but increase. This is one of the reasons we add .XY to the PR instead of increasing it by one.
OpenEmbedded has a versioning policy but is not following it. We have to fix that for them, sometimes we need to bump the PE to make the upgrade working.
With merging early and often (regularly like every week) the adjustments we have to make and test should be managable.