Ian Boston wrote > > I have done a patch[1] that reverts the changes and makes a release of all of > the above possible. It builds, release:prepare works (but needs base to be > released first so that server can bind to 2.0.6) and I have tested it in our > custom environment with all our Ruby based integration tests. I might have > missed something but there were no errors. > > I would propose that we apply the patch (might be best if I do this from > git->svn so deletes/moves/renames behave), > release the items (Carsten?, just because your keys are better signed than > mine) > and if it looks like the vote is going to pass (ie 3 committers have done > validation) > then revert the patch (I can do this git->svn) to allow JR2 move to happen. > Sounds good to me with some additional comments :)
- I can do the releases - We have to properly reschedule the jira issues (volunteer?) And > 908956 SLING-1366 : Use dynamic proxy to handle session#impersonate call. I think this one should go into the release as this fixes a broken implementation. There is currently a line in there which excludes the pre jsr 283 interfaces. So we should remove this line. Regards Carsten -- Carsten Ziegeler [email protected]
