|[cross-project-issues-dev] LTS releases (was Re: 6 month release cycle)|
The true nature of the LTS has been very poorly disseminated with the result that everyone is very confused. At EclipseCon France I think I succeeded in getting to the bottom of my mis-expectations.
a) The LTS will not provide any further releases. i.e. no SR3, SR4, SR5 etc.
b) The LTS provides no publicly accessible repositories for fixes
c) The original committers have no commit rights for LTS activities
(NB this is right: maintaining code with paranoid stability requires a very different mind-set to developing code).
a) The LTS coordinates maintenance teams to provide legacy fixes
b) All fixes are publicly available via Bugzilla
c) LTS builds will be proprietary and just a pick and mix of those bug fixes that are important to the company doing the build
Any company is able to create a proprietary Eclipse release today and charge customers for it. This is exactly what will happen in LTS. The difference/improvement is that those companies interested in having in-house LTS releases pool their efforts to fix legacy bugs and make those fixes available individually.
On 03/07/2013 18:30, Jesse McConnell wrote:
Back to the top