Release issueshttps://lab.civicrm.org/dev/release/-/issues2021-09-21T21:01:40Zhttps://lab.civicrm.org/dev/release/-/issues/8D8 composer installation method for ESR versions2021-09-21T21:01:40ZjackrabbithannaD8 composer installation method for ESR versionsSince only those folks that chip in and pay into the ESR problem have access to the CiviCRM ESR tarballs, there should be a composer based method that will always provide "the latest ESR release" ..
IDK how this can be done. Will CiviCR...Since only those folks that chip in and pay into the ESR problem have access to the CiviCRM ESR tarballs, there should be a composer based method that will always provide "the latest ESR release" ..
IDK how this can be done. Will CiviCRM need a private packagist account that people that pay into the ESR can use to composer require the ESR version?
If CT ends up not providing a ESR composer method ... Skvare may provide a how-to for how to :
1) install the latest ESR version, and a process for updating the ESR version ...
Target for this should be ESR 5.13, which I believe will be the next ESR?https://lab.civicrm.org/dev/release/-/issues/7Publish the zetamailcomponents-mail fork on Packagist?2019-04-04T12:29:07ZbgmPublish the zetamailcomponents-mail fork on Packagist?Follow-up to https://lab.civicrm.org/dev/drupal/issues/36: since we cannot un-fork, can we publish our fork on Packagist?
This would help simplify the composer workflow, assuming we could then run `composer require civicrm/zetacomponent...Follow-up to https://lab.civicrm.org/dev/drupal/issues/36: since we cannot un-fork, can we publish our fork on Packagist?
This would help simplify the composer workflow, assuming we could then run `composer require civicrm/zetacomponents-mail` instead of having to edit the `composer.json` file manually.tottentotten