On Wed, Jul 10, 2013 at 08:44:24PM +0000, Alex Huang wrote: > Thanks Chip for starting this thread. > > I can at least think of the netapp plugin integration as something that was > tried before ASF but no longer tested and used. >
Awesome, that's one. Any others? > I'm all for coming up with this list but I don't see how this list can be > conclusive. The problem that Edison dealt with in swift support is very > real. I'm not trying to make an excuse for making a unilateral decision to > drop support without getting community feedback first. That is wrong and I'm > glad it's being resolved. However, without automated testing backing > functionality, we can have different set of these problems pop up every > release. Should we start with only functionalities tested in automated > testing to be the supported feature set and add features back in as more > testing is added back in? > > To that end, how much of 4.0/4.1/4.2 features are actually added to automated > testing? Or else we can face the same problem with those features too. > > I still support gathering this list, even if it might be inconclusive. I agree with your points above, but think that we need to take this step by step. Let's figure out what code isn't actually in shape, based on historical understanding first. We then at least have a target to ask the next question: what's covered by testing (automated or manual) for each feature release? Then we have a list of areas to focus on for automated testing. > > --Alex
