Hi, Clearly, I already did some changes in Sitetool API. And what we are discussing in DOXIA-482 regarding comments in source markup not to translate into output markup is not what I would call "important".
But for sure, as we discussed in some Jira issuees, if we want new versions of skins to use new features we're adding to Doxia Sitetools, we'll have to clearly document that some new skin versions will require some Doxia Sitetools minimum versions, then some minimum maven-site-plugin So I don't have strong opinion on naming next Doxia+SItetool version 1.7 or 2.0: if someone feels that it will be more clear to name it 2.0, why not. Why I want to avoid is to remove features in this version, that would break old skins versions running on newer maven-site-plugin/Doxia Sitetools: that's when we remove feature that versionning becomes more crucial IMHO. At the moment, when adding features, we're just re-discovering that new features can be used by newer skins only if requirement is properly documented, which is not in our habit on this Regards, Hervé Le dimanche 3 janvier 2016 19:04:58 Michael Osipov a écrit : > Hi folks, especially Hervé, > > we're discussing several important changes in how stuff is going to be > processed in Doxia. Some of them will introduce cleanups and necessary > compat breaks. Wouldn't it be wise to bump to a new major 2.0 which is > going to be the last supported for Maven 2.x? 3.0 would be Maven 3.0 > only. This would allow us to rectify breaking changes in the first place. > > WDYT? > > Michael > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
