Now that we are relatively close to upstream OE, it is preferable to submit fixes upstream instead of forking or appending OE code within OpenXT, which would incur maintenance costs.
If OpenXT master is tracking OE master, no backport is needed.
If OpenXT master is behind OE master, or if an OE fix is needed for a stable release of OpenXT, an OE backport may be needed.
When an OE fix is made to an upstream .bbclass file, the backport can be incorporated into OpenXT by a layer of higher priority than OE core. When OpenXT moves to an OE release which includes the fix, backported files can be dropped from the layer.
This ticket is for discussion of OpenXT requirements for an OE backports layer, e.g. separate repo, subdirectory of existing repo (xenclient-oe, openxt-platform), new versioning model: https://groups.google.com/forum/#!topic/openxt/jgP-cz3IT0M