For Eclipse as a product it is definitely good to have releases more often. It will lower the entry barrier (patches could find a way in the release in less then a year), and will attract new contributors.
BUT at the same time there is Eclipse as a platform, with API compatibility, with service releases and specific change management policies, which is totally different from the Eclipse-As-A-Product. So, maybe the key point is that there is a need for two lines: - release train, kept as it is currently - rolling release - it is a product. rather for users then for developers. New API and features can be withdrawn. -- Krzysztof Daniel <kdan...@redhat.com> Red Hat _______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
