Uploaded image for project: 'Zanata'
  1. ZNTA-1391

Merge zanata-parent,-api,-common,-client with zanata-server

    Details

    • Type: Task
    • Status: Closed (View workflow)
    • Priority: unspecified
    • Resolution: Ready for Release
    • Affects Version/s: None
    • Fix Version/s: platform-4.0.0
    • Component/s: None
    • Labels:
      None

      Description

      As described in ZNTA-770 Closed , having multiple repositories is affecting our ability to do continuous integration, and to test changes which require api, server and client to be modified together ("synchronised pull requests").

      Back in 2012, the idea of splitting these repositories was to allow them to follow different lifecycles, but in practice they always tend to be released together anyway (see for example Zanata 4.0.0-alpha-1), especially as we try to move towards continuous delivery.

      We need to look at putting them all back in a single repository. This should make our release scripts far simpler, and avoid problems like server pointing to the wrong api snapshot, or changes in api breaking the server build.

      git subtree add could be used for this, but the resulting git history for individual files is not good (and existing pull requests would probably become modify/delete conflicts).

      I think the best option for us is git remote add, mv, merge:

      NB: This wiki page will become obsolete: https://github.com/zanata/zanata-server/wiki/Git-Submodules

        Attachments

          Issue links

            Activity

              People

              • Assignee:
                sflanigan Sean Flanigan
                Reporter:
                sflanigan Sean Flanigan
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: