2013/8/6 Darrell Anderson <darrella@hushmail.com>
I don't pretend to understand the programming reasons cited above.
I've probably done the most user testing with Tim. I've been using
GIT pre-R14 for many months and I am not seeing any serious
problems with tdehwlib. Whether the sources need to be moved to a
separate module ultimately gets decided by Tim as he is the owner
of that code.
Everything I wrote is my plans and view of the situation. I've just intended to start a discussion...
Sorry if it was sound too strongly.
Even if Tim wants to move tdehwlib to a separate module, I vote not
to do that until after R14.0.0 is officialy released. Simply
because we have enough on our plate right now to get R14.0.0 out
the door. Although we are planning regular maintenance updates for
R14.0.0 (R14.0.1, R14.0.2, etc.), ABI changes mean a bump in the
second part of the version number: R14.1.0. There is no reason we
can't do that as long as there is consensus that is what we want to
do.
I agree, it won't get into R14.0 branch. But I glad to here that it's ok to make API changes in R14.1, so we won't have to wait until R15.
Just my two cents. :-)
Darrell