Uploaded image for project: 'eZ Publish / Platform'
  1. eZ Publish / Platform
  2. EZP-21562

Create separate synchronized repositories for API and SPI

    Details

    • Sprint:
      Ventoux Sprint 3
    • Story Points:
      2

      Description

      Having separate (read-only) repositories would help bundles developers a lot by making them require only our API/SPI interfaces when needed.

      Typical use case is the REST client in PHP. It's completely pointless to make it require the whole ezpublish-kernel repository.

      We can get inspired by what Symfony does with their components. Everything is committed in the main repository, but components are accessible separately thanks to synchronized repositories.

      Example is HttpFoundation:

        Issue Links

          Activity

          Hide
          Gaetano Giunta (Inactive) added a comment -

          interesting approach!

          (troll)whish zetacomponents did that, for the opposite reason: being able to doanload all of them at once!(/troll)

          Show
          Gaetano Giunta (Inactive) added a comment - interesting approach! (troll)whish zetacomponents did that, for the opposite reason: being able to doanload all of them at once!(/troll)
          Hide
          Bertrand Dunogier added a comment -
          Show
          Bertrand Dunogier added a comment - ezpublish-kernel#684
          Hide
          Bertrand Dunogier added a comment -

          Pull request merged. See the description for details.

          Show
          Bertrand Dunogier added a comment - Pull request merged. See the description for details.
          Hide
          Paulo Nunes (Inactive) added a comment -

          No QA Needed

          Show
          Paulo Nunes (Inactive) added a comment - No QA Needed

            People

            • Assignee:
              Unassigned
              Reporter:
              Jérôme Vieilledent (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 2 days Original Estimate - 2 days
                2d
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 2 days, 1 hour
                2d 1h

                  Agile