On Feb 26, 2013, at 1:51 PM, Eli Collins wrote: > it doesn't seem right to hold up 347 up for Windows support given that > Windows support has not been merged to trunk yet, is not in any Apache > release, etc. Personally I don't like establishing the precedent here > that we can hold up a merge due to requirements from an unmerged > branch.
It is not being held back of for the windows port. It is being held back because 2246 should not be removed as part of 347; a separate jira should had been filed to remove it. Chris argues well in an earlier email to remove 2246 on its own time and that there is precedent for doing so: Snippet of his email below: On Feb 20, 2013, at 4:29 PM, Chris Douglas wrote: > There's > ample precedent for retaining obscure, clumsy features as a temporary > stop-gap (e.g., service plugins, opaque blobs of bytes in Tasks, > configurable combiner semantics). What's the virtue of insisting on > removing this? sanjay
