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

Ensure db updates are run for 5.3.alpha1 #12425

Merged
merged 1 commit into from
Jul 6, 2018

Conversation

seamuslee001
Copy link
Contributor

ping @eileenmcnaughton @totten @monishdeb this is for the RC with the RC all we need to do is to add this then anyone once the 5.4 tarball comes out will get smooth upgrade from 5.2 upwards using the 5.4 tarball

@civibot
Copy link

civibot bot commented Jul 5, 2018

(Standard links)

@eileenmcnaughton
Copy link
Contributor

@seamuslee001 this is effectively a port of a patch already merged to 5.3?

@seamuslee001
Copy link
Contributor Author

Correct but i haven't done anything about copying the contents of what is still in the 5.3.alpha1.mysql.tpl file

@eileenmcnaughton
Copy link
Contributor

OK seems fine - seems like this is fine for 5.4 but if we decide to forward merge the security changes we will need to be wary of this

@seamuslee001
Copy link
Contributor Author

Merging as per the tag

@seamuslee001 seamuslee001 merged commit 863643d into civicrm:5.4 Jul 6, 2018
@seamuslee001 seamuslee001 deleted the 5_3_alpha1_fix branch July 6, 2018 01:13
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.

3 participants