Am 04.03.2013 um 17:30 schrieb Stefan Negrea:
I am not sure how this would work from the perspective of getting a
build out for testing purposes. The fix for core might break something else in the plugins
space but there is no way to get feedback for the change in core until post-release of
core itself. Since the test driver in this case would be a change or new functionality in
a
Isn't that perfect?
If we make a change in core that breaks (our) plugins, it is likely to break plugins of
third parties as well, which is one thing
we are seeking to prevent.