On Wed, Feb 25, 2009 at 7:03 AM, Craig L Russell <[email protected]> wrote: > > On Feb 24, 2009, at 11:31 AM, Bill Stoddard wrote: > >> Donald Woods wrote: >>> >>> No idea. It had already been created before I started working on >>> Geronimo. >>> >>> From the ASF page - >>> http://www.apache.org/foundation/how-it-works.html#incubator >>> it sounds like sub-projects should go through the incubator, so maybe we >>> should just create a branch for tooling under the existing openjpa project >>> and just handle it just as another OpenJPA binary release with its own JIRA >>> component for bug/feature tracking and not deal with the sub-project process >>> overhead for now.
FWIW with subversion, i tend to prefer (where possible) to create a new area and use svn:externals to pull in the current code >> No need to go through the incubator to create a tooling sub-project for >> OpenJPA. Maybe 'sub-project' is not quite the right term here, but the >> point is that the OpenJPA team can carve out svn space to develop and >> maintain OpenJPA Eclipse tooling and you can package/release that stuff >> however you see fit (usual caveats apply). No need for incubator foo here... > > +1 +1 note that (of course) any code imports need to register the paperwork using the lightweight procedure on http://incubator.apache.org/ip-clearance/index.html - robert
