Kuali Mobility
  1. Kuali Mobility
  2. MOBILITY-159

DOC Best practices for managing institutional and kuali source concurrently

    Details

    • Type: Task Task
    • Status: Open Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 2.0
    • Fix Version/s: 3.3
    • Component/s: Marketing
    • Labels:
    • Rank (Obsolete):
      3335
    • Global Rank:
      15854
    • Sprint:
      Mobility 3.2

      Description

      Find a consensus on a best practice for managing two parallel projects in separate version control systems. It is our working assumption that all institutions will maintain their local installation in a local version control system.

        Activity

        Hide
        Joe Swanson (Inactive) added a comment -

        Document the process currently in use at Michigan as a starting point for discussion.

        Show
        Joe Swanson (Inactive) added a comment - Document the process currently in use at Michigan as a starting point for discussion.
        Hide
        Kevin Kronenbitter added a comment -

        What we have done at Cornell for our Rice and KFS implementation is to maintain a single repository of institutional changes. This project uses a Maven Overlay with the foundation code as a dependency. This has worked well for us with these projects.

        Show
        Kevin Kronenbitter added a comment - What we have done at Cornell for our Rice and KFS implementation is to maintain a single repository of institutional changes. This project uses a Maven Overlay with the foundation code as a dependency. This has worked well for us with these projects.

          People

          • Assignee:
            Unassigned
            Reporter:
            Joe Swanson (Inactive)
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:

              Agile

                Structure Helper Panel