15 Oct
2009
15 Oct
'09
7:59 p.m.
Daniel-Constantin Mierla writes:
Since K 3.0 has pretty tight schedule in release
policy, some of these
patches go first there, but can be ported to sr3.0 if people find them
useful and if there are devs having time for them in this period, or
after K3.0 release, either directly or in defines.
in my opinion tight schedule is no excuse to break the one core + tm
policy. now there is two versions of core, which makes testing and bug
reporting much more difficult. i'm not going to use k version of core
and this kind of rule breaking makes me feel very bad about the whole
project.
-=- juha