Hi Felix, >>> > > * jackrabbit-classloader: There isn't much work going on here, apart >>> > > from bugfixing. So there will be no reasons for new releases ! >> > >> > Even bug fixes need to be released. Are you suggesting we just drop >> > the component? > > Definitely not, there will be bugfixes and we will not drop this. But we > should certainly not raise the version number and create new releases > just for fun. I would say the classloader component is largely in > maintenance mode at the moment. > [...] > Again: No changes, no release, no management. Therefore we should strive > for this separation.
I don't quite understand how you would want to handle these "no release" components. Just depend on the released 1.4 version and delete the code from trunk? Or move them to a separate component in the trunk already? The latter requires a new component build process, hence effort. Where should issues be reported? To the JIRA for the "main" cluster, where there is still a JIRA component for the spun-off code? Or create the new JIRA project right away? That would imply effort again, at least at Infra. And if you don't do the preparations right away, you'll face a steep hill to climb if there is need for a new release. A reasonable approach seems to be to start with the undisputed components (JCRAPI, JCRSPI, JCRRMI) and learn by doing how much effort it is. Additional projects can always be spun off from the "main" cluster later. cheers, Roland
