The_Matrix
Guest
see Mark.. .in fact, correct the kiss and send me the correction thus repairing the kissed version that was sold for good. then when you have put the trunks in place and the version is stable release the new (and you start again with the basins) and give the user the stable version the ability to work until you want it with a product that works. the euro of the transfers that are made you work very well, do not forget it.
try to think if faced with kissed software they paid you the salary with a part of euros in turn kissed.. .
But I understand that now this logic of releasing products that work, but also not, has become established practice for the precise planning in this sense of software houses that write licensing agreements putting black on white that software can work. . but also not.
Sooner or later, I'm sure, there will be some judge who will put you in line or, alternatively, with his butt on the ground. :smile:
from "outside" is simple to comment. (aka "it's easy to fag with others' ass" :biggrin

when you adopt a software version, we already work on the next one or even two.
there are corrections that can be made in the current version and others that is not possible because the impact would be too big.
a bit like when complaining that 156 had a too high steering radius: to correct this "defect" (due to the geometry of multilink suspensions adopt) did 159, not a 156.2...
this applies to us and to all.
software, volents or nolents, have become "elephantiaci" and above all, are composed of many "pieces", not all produced by the software house.
so not everything is under our control.
do you know that nx has at least 200 "parts" provided by third-party companies?
However, this is the world of software. We wait for the famous judge.:finger: