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

CRM-21595 re-fix CRM-21445 #11454

Closed

Conversation

eileenmcnaughton
Copy link
Contributor

@eileenmcnaughton eileenmcnaughton commented Dec 23, 2017

@MegaphoneJon
Copy link
Contributor

FWIW I applied this fix to an affected site and can confirm that it fixes the problem.

@colemanw
Copy link
Member

@eileenmcnaughton I'm confused about this PR. It's against the 4.7.29.rc branch but that version has already been released.

@seamuslee001
Copy link
Contributor

@eileenmcnaughton this should really go against 4.7.30-rc given that 4.7.29 has been released

@MegaphoneJon
Copy link
Contributor

@seamuslee001 @colemanw Eileen suggested that 4.7.29 be re-cut and the existing download replaced on account of this being a critical bug - it causes contribution/event pages to fatal/WSOD. She said this here: #11427 (comment)

I'm not taking a position one way or another on that - I don't know everything I should in order to have a useful opinion. Since she's on holiday, I wanted to make sure her position was represented.

@yashodha
Copy link
Contributor

@MegaphoneJon I agree. Its much more critical bug and will affect users badly. We might also want to put up a blog post to notify unsuspecting users hold off upgrade till next plans are figured out.
@colemanw @eileenmcnaughton @totten Thoughts?

@seamuslee001
Copy link
Contributor

Yeh i see the point i guess we haven't had a practice of re-uploading a tar ball but given how critical this is it might be worth it. However if we get it into 4.7.30-rc then its only about what 2 weeks off that release.

I certainly don't know what is the best course of action here. I agree with Yash that we need core team's input

@seamuslee001
Copy link
Contributor

Jenkins re test this please

1 similar comment
@seamuslee001
Copy link
Contributor

Jenkins re test this please

@eileenmcnaughton
Copy link
Contributor Author

Due to the criticality of this I have merged to 4.7.30 & master - #11483 - however, I still advocate replacing the 4.7.29 tarball with one with this fix asap

@eileenmcnaughton
Copy link
Contributor Author

too late for this now - closing

@eileenmcnaughton eileenmcnaughton deleted the process_arg branch January 21, 2018 22:34
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.

6 participants