[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [eclipselink-dev] New Components in EclipseLink
|
Hi Doug. The Technology PMC approves the creation of these components
and the reorganization of existing functionality into these components.
FWIW (and for future reference), adding new functionality requires that
we notify the membership [1] per section 4.3 of the Eclipse Development
Process [2]. Since you're not adding new functionality, this doesn't
apply.
Wayne
[1] http://www.eclipse.org/projects/dev_process/notifying-membership.php
[2] http://www.eclipse.org/projects/dev_process/development_process.php
On Thu, 2008-02-28 at 12:06 -0500, Doug Clarke wrote:
> Technology PMC,
>
> We would like to add some new components to the Eclipse Persistence
> Services Project to better represent our various functional areas and
> enable easier bug filing and tracking in bugzilla.
> http://wiki.eclipse.org/EclipseLink/Components
>
> Can you please approve the creation of these 4 components:
>
> SDO
> Service Data Objects (SDO) implementation.
>
> The implementation already exists in the repository as part of
> the initial source contribution (CQ 1604)
> Utils
> A set of utilities to assist consumers with their use of
> EclipseLink. These utilities include migration from other ORM
> solutions, test clients, and the standalone Mapping Workbench.
>
> The migration utility's package-renamer functionality was
> contributed as part of CQ 1604 and the workbench was
> contributed under CQ 1792
> Documentation
> This component is intended to enable the tracking of bugs and
> future enhancements against the large quantity of
> documentation that we are managing in the Eclipse wiki
> (wiki.eclipse.org/EclipseLink/UserGuide)
> Examples
> One of the key success criteria of a runtime framework is
> providing access to a rich set of examples that consumers can
> try to quickly gain knowledge of how the various persistence
> services and features work. This component will deliver a
> comprehensive set of examples maintained and tested for each
> milestone and release.
>
> Doug Clarke
> EclipseLink Project co-lead
> _______________________________________________
> eclipselink-dev mailing list
> eclipselink-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/eclipselink-dev
