Closed dchandekstark closed 10 years ago
@jcoyne requests that we wait to merge this until Rubydora 1.7.3 is out.
Also, hydra should never be pinned to a specific patch level, because that would preclude fixes from being introduced. (without a new version of hydra)
I say we just close this, because it should make no difference now that 1.7.3 is out.
@jcoyne Re pinning hydra to specific patch levels, I might agree if we had a better process for insuring that patches don't break hydra. Maybe we need a release policy for core components that they are tested against the relevant release of hydra ... if so, can we automate that?
@jcoyne @awead Re rubydora 1.7.3, we still have an issue IIRC with 1.7.1. Do we need to yank 1.7.1, or add != 1.7.1 to hydra deps?
Pin rubydora to 1.7.0