On 27/06/13 06:10, Andrew Stitcher wrote:
Last week we has a small (number of people) but aomewhat heated
discussion about removing some pieces of deprecated and obsolete QMFv1
code; and removing the qpid::client header files so that no one can use
this API outside the qpid build itself.
I wouldn't have called it heated :-) Seriously though I'd like to hope it was more constructive than heated - my intention was mainly to fly a "user focussed" flag and certainly wasn't to annoy/irritate/otherwise upset anyone, if anything I suggested did come across as heated then I apologise.

There was some grumbling about the QMF removals, but no conclusive
reason not to as far as I could tell.
Again comments made weren't intentionally "grumbly" rather they were to flag my preference for what might be considered a defined "decommissioning strategy".

FWIW I really like what you're suggesting below (and for autotools). Indeed I'd like to propose that the project adopts this approach in general as a model for "decommissioning" capabilities, I think that adds clarity if we follow a common approach for this sort of thing.

So, the call to vote:
[X] * 0.24 release note as above
     * Notice to user list as above
     * Apply the change in [1] to the trunk of the tree after 0.25 has
       opened.
[ ] Not a good idea, because we're doing/we know someone who is
     doing ... and they won't be able to do ... any more and this is
     why ...

-- Note that I do think that if there is a major lack in capability
    without these APIs etc. then we should put of this removal until
    we can supply the capability with the supported APIs, but I think we
    would need some concrete work items to block the removal.

Thanks

Andrew

[1] https://reviews.apache.org/r/12006/


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to