Re: Oak, Launchpad 8, Docker
Am 02.10.15 um 11:19 schrieb Robert Munteanu: > On Fri, 2015-10-02 at 10:53 +0200, Carsten Ziegeler wrote: >> Am 30.09.15 um 23:26 schrieb Robert Munteanu: >> >>> I think the big one is >>> >>> UserAdmin and GroupAdmin groups are missing on our Oak setup >>> https://issues.apache.org/jira/browse/SLING-3144 >>> >>> There are more details in the issue but the basic idea is that Oak >>> does >>> not and will not support them. >>> >>> My suggestion is: >>> >>> - remove the metatype from the service exposing these parameters ( >>> AuthorizablePrivilegesInfoImpl ) >>> - warn if a non-default value is found set for these properties >>> - no longer take the properties into account >>> - delete the ITs which exercise this functionality >>> >> I don't really understand what the issue is. Is it correct that we >> still >> can have an implementation of AuthorizablePrivilegesInfo with Oak? >> The >> problem is more that the implementation of that one can't be >> configurable? > > Yes, the implementation will still exist, just that the items that were > configurable with Jackrabbit - UserAdmin and GroupAdmin - no longer > exist, therefore it no longer makes sense to expose them. > Ok, then I think we should follow your radical approach from above. Thanks Carsten -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
Re: Oak, Launchpad 8, Docker
On Fri, 2015-10-02 at 10:53 +0200, Carsten Ziegeler wrote: > Am 30.09.15 um 23:26 schrieb Robert Munteanu: > > > I think the big one is > > > > UserAdmin and GroupAdmin groups are missing on our Oak setup > > https://issues.apache.org/jira/browse/SLING-3144 > > > > There are more details in the issue but the basic idea is that Oak > > does > > not and will not support them. > > > > My suggestion is: > > > > - remove the metatype from the service exposing these parameters ( > > AuthorizablePrivilegesInfoImpl ) > > - warn if a non-default value is found set for these properties > > - no longer take the properties into account > > - delete the ITs which exercise this functionality > > > I don't really understand what the issue is. Is it correct that we > still > can have an implementation of AuthorizablePrivilegesInfo with Oak? > The > problem is more that the implementation of that one can't be > configurable? Yes, the implementation will still exist, just that the items that were configurable with Jackrabbit - UserAdmin and GroupAdmin - no longer exist, therefore it no longer makes sense to expose them. Robert
Re: Oak, Launchpad 8, Docker
Am 30.09.15 um 23:26 schrieb Robert Munteanu: > I think the big one is > > UserAdmin and GroupAdmin groups are missing on our Oak setup > https://issues.apache.org/jira/browse/SLING-3144 > > There are more details in the issue but the basic idea is that Oak does > not and will not support them. > > My suggestion is: > > - remove the metatype from the service exposing these parameters ( > AuthorizablePrivilegesInfoImpl ) > - warn if a non-default value is found set for these properties > - no longer take the properties into account > - delete the ITs which exercise this functionality > I don't really understand what the issue is. Is it correct that we still can have an implementation of AuthorizablePrivilegesInfo with Oak? The problem is more that the implementation of that one can't be configurable? Regards Carsten -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
Re: Oak, Launchpad 8, Docker
+1 in general. I think there are some open issues to finalize the Oak stuff? I would like to get the slingshot sample into the launchpad as another nice sample, but that should be easily doable. Regards Carsten Am 30.09.15 um 07:56 schrieb Robert Munteanu: > Hi, > > Almost one year ago we release Launchpad 7. Since we aim to release > once per year, looks like a good time to start the release talks. > > I think we discussed several times moving to Oak by default or even > dropping Jackrabbit 2.x support, so my proposal would be: > > 1. Deprecate + drop all features which are Jackrabbit-only > 2. Do a release of the oak-server bundle > 3. Release Launchpad 8 > > When starting the 8 release I suggest that we start with the releases > that we have in the launchpad at that moment, instead of chasing all > SNAPSHOTs and releasing them last year. I will ask when the release > starts, but if anyone thinks that we need a not-yet-released fix > included let's release it then. > > 4. Create a docker image > > I was considering putting up a Sling 8 Oak image on Docker Hub after > the release, so people can get a quick(er) start with it. If anyone > thinks that's not suitable for any reason, please let me know. > > Thanks, > > Robert > -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
Re: Oak, Launchpad 8, Docker
+1 On Tue, Sep 29, 2015 at 10:56 PM Robert Munteanuwrote: > Hi, > > Almost one year ago we release Launchpad 7. Since we aim to release > once per year, looks like a good time to start the release talks. > > I think we discussed several times moving to Oak by default or even > dropping Jackrabbit 2.x support, so my proposal would be: > > 1. Deprecate + drop all features which are Jackrabbit-only > 2. Do a release of the oak-server bundle > 3. Release Launchpad 8 > > When starting the 8 release I suggest that we start with the releases > that we have in the launchpad at that moment, instead of chasing all > SNAPSHOTs and releasing them last year. I will ask when the release > starts, but if anyone thinks that we need a not-yet-released fix > included let's release it then. > > 4. Create a docker image > > I was considering putting up a Sling 8 Oak image on Docker Hub after > the release, so people can get a quick(er) start with it. If anyone > thinks that's not suitable for any reason, please let me know. > > Thanks, > > Robert >
Re: Oak, Launchpad 8, Docker
On Wed, 2015-09-30 at 09:22 +0200, Carsten Ziegeler wrote: > I think there are some open issues to finalize the Oak stuff? I think the big one is UserAdmin and GroupAdmin groups are missing on our Oak setup https://issues.apache.org/jira/browse/SLING-3144 There are more details in the issue but the basic idea is that Oak does not and will not support them. My suggestion is: - remove the metatype from the service exposing these parameters ( AuthorizablePrivilegesInfoImpl ) - warn if a non-default value is found set for these properties - no longer take the properties into account - delete the ITs which exercise this functionality A less drastic approach is - remove the metatype from the service exposing these parameters ( AuthorizablePrivilegesInfoImpl ) - warn if a non-default value is found set for these properties - take the properties into account if the repository is Jackrabbit ( not Oak ) - keep the ITs which exercise this functionality restricted to Jackrabbit ( like we to today ) I would personally go for the drastic approach since we intend to stop supporting Jackrabbit 2.x, but I would like to know what others think about this. Robert