[Dev] Maintaining upstream project with tizen/upstream branches?

Tomasz Olszak olszak.tomasz at gmail.com
Mon Dec 16 23:31:35 GMT 2013


Hi,

I have following case:
Qt Tizen integration is developed and reviewed in Qt project. It is done in
wip/tizen branches (wip = work in progress). These branches are upstream
branches from Tizen perspective. Therefore I've made following assumptions:

1. It is allowed to rebase tizen branch with upstream from time to time for
clarity
2. It is allowed to fast forward (without codereview) upstream branch to
HEAD of tracked branch outside tizen.org.
3. It is allowed to merge tizen branch with upstream without codereview.
4. Changes related to packaging (patches for the upstream code, spec files,
rpm macros inside the packaging directory) should go through formal
codereview process.

I would like to kindly ask to confirm if they are alright or point out the
wrong ones.

-- 
regards,
Tomasz Olszak
Qt for Tizen | http://qt-project.org/wiki/Tizen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tizen.org/pipermail/dev/attachments/20131217/cd7f1cb0/attachment.html>


More information about the Dev mailing list