| We are committed to staying up to date on clj-parent, so we should bias towards a fail-fast method of taking up the new clj-parent versions immediately and dealing with the fallout, rather than waiting until near releases to upgrade clj-parent and potentially discovering problems later. Due to the relatively limited testing that happens before a clj-parent release, this could introduce some instability, but the additional time before a release to deal with any issues is a strong bonus. We can always increase the amount of testing done on a clj-parent PR if stability becomes an issue. |