Closed dsnopek closed 6 years ago
@pwolanin @fluxsauce Any chance of this one getting merged?
In our vanilla Drupal 6 fork, we incremented the version number to 6.41 which I didn't do here because I don't know how Pressflow wants to handle version numbers.
Thanks!
@dsnopek how did you get up to 6.41?
We should probably increment the version here.
@dsnopek how did you get up to 6.41?
Bug fixes after testing on live customer sites :-) We haven't gotten any new issues reported in over 24 hours. We could wait a little longer to see if more come in, so Pressflow doesn't end up doing any bug fix releases? But that's up to the maintainers, depending how to balance getting the security fix out versus potential regressions
We should probably increment the version here.
Ok! To what version? 6.41 to match the vanilla release? Or 6.39 so their aren't skipped versions?
Are there other fixes we should pull into pressflow?
This PR is up-to-date with the latest patch for SA-CORE-2018-001 - through the magic of git commit --amend
the commit has an old timestamp.
We don't have any other core patches. I saw that catch is working on a security hardening thing here, which would probably be good to get into Pressflow eventually, but I don't know how that's going.
Let's go to 6.39 here
Version updated!
See https://www.mydropwizard.com/blog/drupal-core-security-update-sa-core-2018-001-including-drupal-6