Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adopts to latest When package #14903

Closed
wants to merge 1 commit into from

Conversation

agileware-pengyi
Copy link
Contributor

@agileware-pengyi agileware-pengyi commented Jul 29, 2019

Overview

Adopts to the latest When package. The current bundled When package may generate wrong recurring dates. This PR is just an idea for updating the dependencies and requires the When package updated first.

For example:
setting
result

Before

Wrong recurring dates in some cases.

After

Correct dates with the above settings.

Comments

Any testing required for this one?

Agileware ref: CIVICRM-1223

@civibot
Copy link

civibot bot commented Jul 29, 2019

(Standard links)

@civibot civibot bot added the 5.15 label Jul 29, 2019
@agileware-pengyi
Copy link
Contributor Author

@seamuslee001 this is the one I mentioned. Thanks.

@seamuslee001
Copy link
Contributor

@agileware-pengyi is there an associated PR for packages should we be looking at getting this in composer?

@agileware-pengyi
Copy link
Contributor Author

@seamuslee001 I just submitted the PR. Not sure how to work with the composer here.

@eileenmcnaughton
Copy link
Contributor

@agileware-pengyi this will need to be against master branch

@agileware-pengyi
Copy link
Contributor Author

@eileenmcnaughton thanks. Will do if this is acceptable.

@totten
Copy link
Member

totten commented Jul 30, 2019

(Seamus) @agileware-pengyi is there an associated PR for packages should we be looking at getting this in composer?

(Pengyi) @seamuslee001 I just submitted the PR. Not sure how to work with the composer here.

Right, as Seamus indicates, there is a choice here to (a) do the upgrade within civicrm-packages.git or (b) migrate to composer.json at the same time as doing an upgrade.

There's fairly limited guidance about this. The file VERSIONS.php has some docs, and I've added a PR to talk more about composer.json migration. See e.g. revised VERSIONS.php with PR.

Either technique is acceptable, but migrating is better in the long-term (involves more upfront risk/time; but going forward, it provides simpler workflow on upgrades and provides better visibility into pkg mgmt).

@totten
Copy link
Member

totten commented Jul 30, 2019

For RecurringEntity BAO changes, it might be good to ping @deepak-srivastava and give a few days to see if he has any thoughts.

@seamuslee001
Copy link
Contributor

It should also be noted that we can't use the When package v3.x because they specify PHP7.1 in their composer.json so you either target master branch with a specific commit before they switched to PHP7.1 or do as Pengyi is doing.

@eileenmcnaughton eileenmcnaughton changed the base branch from 5.15 to master August 14, 2019 23:02
@civibot civibot bot added master and removed 5.15 labels Aug 14, 2019
@eileenmcnaughton eileenmcnaughton changed the base branch from master to 5.15 August 14, 2019 23:02
@civibot civibot bot added 5.15 and removed master labels Aug 14, 2019
@agileware-pengyi agileware-pengyi changed the base branch from 5.15 to master August 14, 2019 23:27
@civibot civibot bot added master and removed 5.15 labels Aug 14, 2019
@eileenmcnaughton
Copy link
Contributor

Superceded by #15223

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants