hi guys, > I think that Sling should be able to run on JCR 1.0 for a long time; we > shouldn't tie us to a new version; however, of course we might have some > optional functionality requiring JCR 2.0. i think we should naturally embrace jcr 2.0, i don't really think that we will have backwards compatibility issues since i would not expect that there are other repositories than jackrabbit that are currently used with sling. so in my opinion we should probably use jcr 2.0 where it makes sense particularly over proprietary jackrabbit apis as soon as they are available in jackrabbit...
thoughts? regards, david
