the filesystem resource provider exists for a long time and is very useful. until version 1.1.4 it supported only the "old" Sling Resource Provider SPI.
in version 1.2.0 it was switched to the new Resource Provider SPI. this was an backwards incompatible change because one of the osgi config properties had to be renamed (provider.roots -> provider.root). i'm currently working on some major improvements (SLING-6440, SLING-6537), and i want to support both the old and the new Resource Provider SPI, so basically I want to fork it and maintain two separate versions. looking back it was not a good idea to release the switch to the new SPI in the 1.x version range because it breaks semantic versioning due to the config property change (i had missed this change as well at that time). my proposal is: - once the implementation is ready release the fsresource provider fork supporting the old Resource Provider SPI as 1.3.0, and further releases as 1.x - release the new version for the new Resource Provider SPI as 2.0.0 the drawback of this proposal is that we have a few older releases in the 1.x line (1.2.0 and 1.2.2) that are not in line with semantic versioning, but this would be fixed in 1.3.0 and upwards. any objections? stefan
