Jonathan Halliday wrote:
Whilst getting at least some functionality out sooner rather than later is probably a good thing, one of my concerns on delivering this in staged releases, potentially including the current cycle, is the impact it will have on docs and QE. We'd need to clearly specify what scenarios are expected to work in each release we provide, in order to test correctly and manage user expectations thoroughly. We probably need an internal discussion with those teams to see what resource they have available in addition to seeing what dev resource we can shake loose for this by deprioritizing other things.
I agree wholeheartedly with Jonathan and also think we definitely need to take heed on his point re functionality available at each stage being documented accurately and the overhead this will add to EAP. Jason, are we certain this is a feature that needs to be in EAP6 vs EAP6.1? I guess more generally can you clarify your preferred and maximum timescales you would like us to deliver this functionality within.
Another point that was raised earlier (or rather a detail of the one surrounding QA) is the question of testing this with remoting itself. Clearly some work will be done on the remoting side to chat with the API we expose so is it realistic to expect this level of testing to be performed in the timescale needed?
It sounds like a nice piece of work, but our worry is we may simply not be able to add this feature with enough capability/testing to address your desired use cases in the timescale we anticipate you need this in. That said we are ready to work on this right now so hopefully we can make an effective solution in the time available.