| Re: [dtp-dev] Some releng decisions to make |
Since I haven’t seen any comments on this thread, I am proceeding with these changes. Item #1 (requiring Java 8) is already done. Next, I will change the version to v2 (all plugins will receive a major version bump) and limit support to neon. - Konstantin
One more related question… 3. What Eclipse versions should we support with the upcoming release. The build is currently configured to build against Neon M2 and to cross-build against Mars and Mars.1 targets. Should we limit the support to Neon? If we should retain support for older Eclipse versions, how far back should we go? It would be good to answer these questions sooner rather than later so that we don’t cause too much thrashing in the Neon aggregation stream. Thanks, - Konstantin
1. I think we should make all DTP plugins require Java 8. Currently, they require Java 5. This change would simplify the build as we would no longer require multiple JDK versions to build. It would have no functional impact on a Neon user since Neon platform already requires Java 8. 2. What should the next DTP version be? If we go with #1, it should be at least v1.13, but if we strictly follow the versioning convention, it should be v2. Raising Java version requirement is a breaking change even if we inherit the decision to move up from the platform. Thanks, - Konstantin |