On Tue, May 25, 2010 at 2:36 PM, Jeff Johnston <jjohn...@redhat.com> wrote: > This was another question that I would like to hear comments on. I was > thinking perhaps 6 months to allow users a reasonable time to migrate and > bug fixes to be made so that is possible. At the moment, we have already > switched to Helios nightly updates and Helios isn't officially out. I > haven't made a branch yet so it isn't currently an issue, but to handle some > of the API violation issues, I will have to. So, either I wait until some > time after Helios is out to make the fixes and branch or otherwise any > subsequent fixes won't be available to current users unless they switch to > Helios immediately.
My philosophy is this... has anyone actually asked you for fixes to be backported yet? If not, I would hold off on this as the burden of maintenance is painful. I'd rather see Linux Tools encourage its users to move up by taking advantage of new APIs unless there's a significant demand requiring old fixes to be backported. In community survey's we have done, there's a good portion of people that move up to the latest Eclipse release pretty quickly. The incentive for your user base to move up should be high :) There's no easy answer but I think Linux Tools is still in incubation (0.5.1 is out) and deserves to be able to move quickly with each release. -- Cheers, Chris Aniszczyk http://aniszczyk.org +1 860 839 2465 _______________________________________________ linuxtools-dev mailing list linuxtools-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/linuxtools-dev
