About release frequency: I am probably the first one who'd like to have a faster release cycle, like twice a year. But, as an integrator point of view, less than 12 months is not acceptable. One stable release per year is already very fast for the market.
In theory, people are not required to migrate to each new release. But in practice, each customer wants to migrate to get benefit for the new features of this new release. That's due to the communication we do around each new release. Experience showed that we need about 4 months of RC's on freezed version. I think we all agree that stability/maturity is more important than new features. So here is the deal: * faster releases -> faster new features integrations, more risks of new bugs * slower releases -> less faster integration of new features, less risks of bugs I agree they are others way to increase the maturity and we are also working on it. (in a few days, we will release our new policies). But it's clear that faster releases will increase the risk of new bugs. @ferdinand Thank you for all your bugs report. I know we fix a lot of them, but we also delay/deny a lot of them. For us, ergonomy changes in the layout of a screen is an improvement, not a bug. We can not take the risk to change this in a stable version. (imagine that others modules may have inherited from the view we change). -------------------- m2f -------------------- -- http://www.openobject.com/forum/viewtopic.php?p=42432#42432 -------------------- m2f -------------------- _______________________________________________ Tinyerp-users mailing list http://tiny.be/mailman2/listinfo/tinyerp-users
