1 Jun
2015
1 Jun
'15
8:56 p.m.
I agree on the strategy; the main thing I want to avoid is lots of
inexperienced users downloading V2 and hitting lots of bugs. I'd
rather the old heads hit them as they know not to panic and just file
bug reports ;)
The question is wether we could arrange for a coordinated testing effort - e.g. make a
list of tests/formats/options to go through, instead of just waiting for bugs to occur.
This list could be worked out in advance. I think that could be the fastest way to get a
first stable 2.x
I would also think that once 1.x is frozen, most contributors would naturally go on to v2
for their testing, translating, etc., because there is little to do for 1.x. Bugs will
only be reported through real-life use for 1.x then.
- Carsten