As planned, with this week's I-build, we are moving all WTP plugins/features be at the 1.0.0 level (up from 0.7.0 or 0.7.1).
While this is being handled "in mass" for WTP plugins and features (so committers don't need to take action)
many adopters may need to react when they adopt I-build or M9.
And, while we're on the topic, I propose that after our WTP 1.0.0 release we begin the more finer grained versioning that is
being proposed in
http://eclipse.org/equinox/documents/plugin-versioning.html
and discussed much in
https://bugs.eclipse.org/bugs/show_bug.cgi?id=99393
Please read ahead and lets anticipate problems and procedures. This will especially be
important to "do right from the beginning" for anyone who's "splitting steams" after
M9 to begin 3.2 based work (and there could be implications even if you don't literally split streams,
just adding stuff for WTP 1.5, that's not in 1.0, would suffice to trigger the new versioning rules).
_______________________________________________ wtp-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/wtp-dev
