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

Improve composer.json's ezplatform behat handling to use semver

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Confirmed
    • Priority: High
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: CI System, Composer
    • Labels:
      None

      Description

      The version of ezplatform that gets installed by Travis to run uses git with a branch name set in composer.json.

      If it could use composer & semver instead, it would have several advantages.

      Taking current ezplatform & repository-forms v1.9 as an example, during development, we can require ^1.9@dev, and it will install master (thanks to the branch-alias). Upon feature freeze, when tagging 1.9 beta1, we don't need to update it before we branch out 1.9. All we have to do is update master to require ^1.10@dev once ezplatform branch-alias has been updated.

      Beta and rc requirements being written only to the tags themselves, we will have the minimal set of changes.

      This at least applies to repository-forms, but can be used by any ezplatform package.

        Attachments

          Activity

            People

            Assignee:
            Unassigned
            Reporter:
            bertrand.dunogier@ez.no Bertrand Dunogier
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated: