On Monday 13 Apr 2015 10:04:05 Mateusz Loskot wrote: > On 13 April 2015 at 09:36, Mateusz Loskot <[email protected]> wrote: > > On 13 April 2015 at 08:18, André Hartmann <[email protected]> wrote: > >>> https://wiki.qt.io/Branch_Guidelines > >>> The latter explains recommendations and caveats of possible > >>> development workflows. > >> > >> But that's only true for Qt itself. > > > > The /Branches article says > > "Qt Creator uses the same branching policy as Qt itself" > > > >> So just push your new plugins to master. > > > > I've been looking for answer on which branch to branch off, thanks. > > I should have clarified, I'm going to work prepare for contribution this > way: - fork Qt Creator on GitHub > - create branch boostbuild-plugin branched off of the master > - import source of my plugin > - work on the plugin integration, apply necessary changes, etc. > - once the integration is completed, submit the plugin through Gerrit > > I hope it's acceptable workflow, as two other developers that joined > my efforts are based on GitHub, and GitHub simlifies our collaboration a > lot.
Every author needs to agree to the Contribution Licensee Agreement, so make sure that everyone that joins you understands and signs that CLA. daniel _______________________________________________ Qt-creator mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/qt-creator
