On 01/10/2016 11:46 PM, Erik Weber wrote:
> What if the fix is part of a refactorization or a new feature? > Providing a LTS is not 'easy as pie' with a product like CloudStack where a > lot of code changes over time. Didn't say it's easy :) Yes re-factorization is one of the unsolved "problems". That is why I wrote, squashing is evil for fixing bugs. It is important that devs fix the bug first, commit and then do the refactor commits If the devs fixed it by "mistake" somehow in the refactor in the past, then we can decide if we can re-implement the fix without refactor (aka it would be "obvious and small"). LTS would not mean we fix all the bugs. > For instance, /if/ the strongswan feature is merged to 4.8, how to you > handle /ANY/ VPN fixes in 4.5 since they don't even use the same software? > And the whole VR process was refactored in 4.6 -- meaning you won't be > using the same scripts, or even the same language. Yes, we must dedicated from fix to fix. How and if. > Even if a bugfix is included in master and tested, it is impossible to say > how it will react with an older/different solution. It depends, for sure testing must also be done. > The same can be said for library updates etc. > > Don't get me wrong, I'm not opposing a LTS version -- actually I would > rather like to have one. I just want to be clear about the fact that it > won't be always be easy, and not all fixes might be possible to backport -- > depending on how strict you'll be with 3rd party stuff. That is fine, I am aware of that. >> * Fix must be important. >> > > Who defines what 'important' is? "must be important" means we do not backport trivial things like typos in docs and so forth, only important things. And I would say important in a common sense. But it doesn't mean that all important fixes will be backportable, because they may not be necessary "obvious and small". > On a last note, doing LTS -- atleast in my opinion -- requires commitment. > Anything called LTS is usually getting a lot of user focus/traction and > have to be rock solid and maintained. That is why I started this thread, I would see a commitment, that _we_ as community provide a LTS for those who need it.
