6 Replies Latest reply on Aug 22, 2011 11:17 AM by Lukáš Fryč

    3rd party dependency management

    Justin Wyer Newbie

      As discussed in this weeks team meeting the requirements for managing 3rd party dependencies are:


      1. Regardless of the state of the upstream project source remains accessible.
      2. Process should be transparent for users (can be managed by richgit.sh if required).


      I recommend we fork (or import to github if upstream project uses another SCM, we may need to update occasionally) the upstream project. At a point in RF development we tag the our fork and this tag is added/updated as a git submodule to the revelent RF project. This fits our git workflow well.


      We should have a wiki page dedicated to this as well as notes in the sandbox project.