A Dilluns, 31 d'agost de 2009, [email protected] va escriure: > In lots of oss projects I'm following, the policy is rather have much > smaller steps and release more often. I personally would prefer 'major' > releases every 6 months. Doing that you could: - really release minor (eg > fully compatible, no regression) versions between those 6 months, - > concentrate API changes, non compatible fixes for the 6 months releases > (because they aren't that far away so it's doable) - have partners working > for the next release most of the time instead of less then 2 months a year. > - have less regression from a major to the next major as they are closer in > term of code.
Please, do not work on 6 month releases. I think it'd kill integrators like us. Most projects take more than six months from analysis to production so adding the overhead of 6 month releases is unmantainable, I'm afraid. IMHO that would only be sensible if API and database compatibility was ensured at the very least for two or three releases. -- Albert Cervera i Areny http://www.NaN-tic.com Mòbil: +34 669 40 40 18 _______________________________________________ Tinyerp-users mailing list http://tiny.be/mailman2/listinfo/tinyerp-users
