On 6/23/05, Sean Schofield <[EMAIL PROTECTED]> wrote: > Right. I remember this was an issue with commons-chain. No > refactoring of Struts to use commons-chain could start until that was > released. Makes sense to me.
It would seem reasonable to be allowed get a jump start on uptaking new, unreleased dependencies from the safety of an isolated feature branch, as long as there is no impact on the branch being used to stablize the release. This can be beneficial if there is a significant amount of work required to consume the new dependency. Once the new dependency is officially released, the private branch can be updated to reference it and then the changes can be safely merged back to trunk, ready for the next release train. Kind Regards, John Fallows.
