This is a process workflow for creating a new [[EMFT]] (or other Modeling project) component.

''In this example, the new EMFT component is EMF JCR Management, or org.eclipse.emf.jcrm. See also bugs [https://bugs.eclipse.org/bugs/show_bug.cgi?id=182379 182379] and [https://bugs.eclipse.org/bugs/show_bug.cgi?id=182380 182380].''

''In this example, the new EMFT component is EMF JCR Management, or org.eclipse.emf.jcrm. See also bugs [https://bugs.eclipse.org/bugs/show_bug.cgi?id=182379 182379] and [https://bugs.eclipse.org/bugs/show_bug.cgi?id=182380 182380].''

−

==Legend==

+

= Legend =

Names in square brackets are assignees. If more than one assignee is listed, the first listed is the principal w/ other(s) as backup.

Names in square brackets are assignees. If more than one assignee is listed, the first listed is the principal w/ other(s) as backup.

* [<b style="color:green">COMP</b>] contact PMC via [[:Category:Modeling_Meetings | meeting]] or [https://dev.eclipse.org/mailman/listinfo/modeling-pmc mailing] [http://dev.eclipse.org/mhonarc/lists/modeling-pmc/maillist.html list] to pitch component idea. Should have a first draft of the proposal doc (.doc, .ppt, .pdf, or ideally, in wiki format) and maybe some sample code at this point

* [<b style="color:blue">WM</b>] change group id on /cvsroot/modeling/org.eclipse.emf/org.eclipse.emf.jcrm.releng/ to emf-jcrm-releng

* [<b style="color:blue">WM</b>] change group id on /cvsroot/modeling/org.eclipse.emf/org.eclipse.emf.jcrm.releng/ to emf-jcrm-releng

+

== Code Contribution ==

== Code Contribution ==

−

* [<b style="color:green">COMP</b>] commit code into /cvsroot/modeling/org.eclipse.emf/org.eclipse.emf.jcrm/ per details in [[EMFT_Procedures | EMFT Procedures]]. Recommend setting plugins to version 0.7.0 if based on EMF 2.2 or 0.8.0 if based on EMF 2.3; or, if code is really new, could start with 0.5.0.

+

* [<b style="color:green">COMP</b>] '''Existing code written by the new committers''' must be submitted to [https://dev.eclipse.org/ipzilla/ IPzilla] for legal clearance before being committed to CVS. Zip all the sources and attach it to the IPZilla. Ensure that proper EPL copyright notices are in place. Document the names of all the people who have contributed to the code. All contributors must agree to the terms of the EPL license for the contribution. Please add the project lead (one of the PMC members) to the IPzilla bug's CC: list so that they can approve it.

−

* [<b style="color:green">COMP</b>] '''Third party''' code must be submitted to [https://dev.eclipse.org/ipzilla/ IPzilla] for legal clearance before being committed to CVS. Note also that many 3rd party libraries are available via the [http://www.eclipse.org/orbit/ Orbit] project, and so can be added to the project at build time (rather than needing to be duplicated in CVS).

+

* [<b style="color:green">COMP</b>] '''Third party code''' must also be submitted to [https://dev.eclipse.org/ipzilla/ IPzilla] for legal clearance before being committed to CVS. Note also that many 3rd party libraries are available via the [http://www.eclipse.org/orbit/ Orbit] project, and so can be freely used in your development workspace and added to the project at build time (rather than needing to be duplicated in CVS). The use of libraries already in Orbit nevertheless requires approval. Each third party library should be filed as a separate IPzilla. Please add the project lead (one of the PMC members) to the CC list for approval.

+

+

* [<b style="color:green">COMP</b>] ''Once cleared by PMC and Eclipse Legal,'' commit code into /cvsroot/modeling/org.eclipse.emf/org.eclipse.emf.<your-component>/ ([[Modeling_Project_Releng/Plugin_And_Feature_Files#Directory_Structure|details here]]). Recommend setting plugins to version 0.7.0 to give you a few years before you have to hit the ominous 1.0.0 release.

== Release Engineering ==

== Release Engineering ==

−

* [<b style="color:orange">REL</b>] add new component to the EMFT website (http://www.eclipse.org/emft/projects/); identify as having no downloads yet

+

* [<b style="color:green">COMP</b>] [[Modeling_Project_Releng/Website_Maintenance | add new component to the EMFT website]]; identify as having no downloads yet

Contents

Legend

Names in square brackets are assignees. If more than one assignee is listed, the first listed is the principal w/ other(s) as backup.

WM = Webmaster(s)

PMC = Project Management Chair

REL = Release Engineer

COMP = Component Owner

Workflow

Proposal

(The proposal submission process is subject to change. If you see anything glaringly wrong here, please correct it.)

[COMP] contact PMC via meeting or mailinglist to pitch component idea. Should have a first draft of the proposal doc (.doc, .ppt, .pdf, or ideally, in wiki format) and maybe some sample code at this point

Bugzilla Setup

CVS Setup

[WM] change group id on /cvsroot/modeling/org.eclipse.emf/org.eclipse.emf.jcrm/ to emf-jcrm

[WM] change group id on /cvsroot/modeling/org.eclipse.emf/org.eclipse.emf.jcrm.releng/ to emf-jcrm-releng

Code Contribution

[COMP] Existing code written by the new committers must be submitted to IPzilla for legal clearance before being committed to CVS. Zip all the sources and attach it to the IPZilla. Ensure that proper EPL copyright notices are in place. Document the names of all the people who have contributed to the code. All contributors must agree to the terms of the EPL license for the contribution. Please add the project lead (one of the PMC members) to the IPzilla bug's CC: list so that they can approve it.

[COMP] Third party code must also be submitted to IPzilla for legal clearance before being committed to CVS. Note also that many 3rd party libraries are available via the Orbit project, and so can be freely used in your development workspace and added to the project at build time (rather than needing to be duplicated in CVS). The use of libraries already in Orbit nevertheless requires approval. Each third party library should be filed as a separate IPzilla. Please add the project lead (one of the PMC members) to the CC list for approval.

[COMP] Once cleared by PMC and Eclipse Legal, commit code into /cvsroot/modeling/org.eclipse.emf/org.eclipse.emf.<your-component>/ (details here). Recommend setting plugins to version 0.7.0 to give you a few years before you have to hit the ominous 1.0.0 release.