Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Kepler Project Plan"
Line 52: | Line 52: | ||
<div style="border: 2px solid #8E87EB; padding: 6px;">Here is a comment. Please feel free to insert your own comments inline below by reusing this markup. ''--Scott Lewis''</div> | <div style="border: 2px solid #8E87EB; padding: 6px;">Here is a comment. Please feel free to insert your own comments inline below by reusing this markup. ''--Scott Lewis''</div> | ||
− | <div id="Milestone 1" | + | <div id="Milestone 1"> |
---- | ---- | ||
Line 63: | Line 63: | ||
==== Collaboration Model Viewer/Editor ==== | ==== Collaboration Model Viewer/Editor ==== | ||
+ | </div> | ||
− | <div id="Milestone 2" | + | <div id="Milestone 2"> |
---- | ---- | ||
Line 75: | Line 76: | ||
==== Integration of Corona Event notifications in Collaboration model ==== | ==== Integration of Corona Event notifications in Collaboration model ==== | ||
+ | </div> | ||
− | <div id="Milestone 3" | + | <div id="Milestone 3"> |
---- | ---- | ||
Line 88: | Line 90: | ||
==== Integration of PDE/Java for generating model from Eclipse projects ==== | ==== Integration of PDE/Java for generating model from Eclipse projects ==== | ||
+ | </div> | ||
− | <div id="Milestone 4" | + | <div id="Milestone 4"> |
---- | ---- | ||
Line 98: | Line 101: | ||
==== Extension point definition to allow tooling to integrate based on Collaboration Model ==== | ==== Extension point definition to allow tooling to integrate based on Collaboration Model ==== | ||
+ | </div> | ||
− | <div id="Milestone 5" | + | <div id="Milestone 5"> |
---- | ---- | ||
Line 110: | Line 114: | ||
==== Integration of Mylyn ==== | ==== Integration of Mylyn ==== | ||
+ | </div> | ||
− | <div id="Milestone 6" | + | <div id="Milestone 6"> |
---- | ---- | ||
Line 121: | Line 126: | ||
==== Meta-data extensions for builds servers ==== | ==== Meta-data extensions for builds servers ==== | ||
+ | </div> | ||
[[Category:Kepler]] | [[Category:Kepler]] |
Revision as of 13:42, 25 August 2007
Proposed by: Jcasey.mergere.com 14:35, 8 December 2006 (EST)
Modified by: slewis at composent.com 14:55, 11 December 2006 (PST)
Commented by: henrik at cloudsmith.com 08:38, 12 December 2006 (EST)
Commented by: slewis at composent.com 12:48, 12 December 2006 (PST)
Commented and Edited by: slewis at composent.com 12:25, 26 December 2006 (PST)
Commented by: thomas at tada.se 17:19, 26 December 2006 (EST)
Updated by: carlos.sanchez at devzuz.com 19:37, 25 August 2007 (CEST)
Contents
- 1 Kepler Project Proposal
- 2 Proposed Schedule
- 3 Notes and Conventions
- 4 Kepler Integration Strategy
- 5 Milestone 1 : Core Model Definition
- 6 Milestone 2 : Adapters and UI
- 7 Milestone 3 : Definition of Collaboration Storage Extensions
- 7.1 Definition of concept of Project Store and Artifact Store
- 7.2 API definitions for Project Store and Artifact Store (WSDL)
- 7.3 UI components for searching Project Store and Artifact Store
- 7.4 Integration of Q4E for generating model for Maven
- 7.5 Integration of PDE/Java for generating model from Eclipse projects
- 8 Milestone 4 : Project Store and Integration Extensions
- 9 Milestone 5 : Integration
- 10 Milestone 6 : Integration of Build/CI Servers
Kepler Project Proposal
Proposed Schedule
NOTE: Notation 'd' signifies the date of Kepler project approval with EMO, since this will keep us from having a code repository, etc. @EF.
NOTE: This proposed schedule is DRAFT and subject to change based upon input from other participants about related project plans and schedules
Milestone | Start Date | Target Date | Comments |
---|---|---|---|
#Milestone 1 | d + 1 week | d + 7 weeks | 1-week delay anticipated to get CVS, other infrastructure setup @EF. |
#Milestone 2 | d + 9 weeks | d + 15 weeks | 1-week delay expected to review/fix process using lessons from first dev cycle. |
#Milestone 3 | d + 16 weeks | d + 22 weeks | |
#Milestone 4 | d + 23 weeks | d + 29 |
Notes and Conventions
- This project should be divided into a series of relatively short milestones, each of which will trigger a new release of the Kepler project once completed. Milestones should be achievable in six weeks, plus or minus one week.
- Files formatted using the (new) native Kepler project model syntax as kmodel-extension files, since they are meant to catch project metadata that cannot be stored in the original metadata files for the project.
Kepler Integration Strategy
NOTE: The general strategy for implementing Kepler deliverables listed below will be integration of existing technologies from both Eclipse projects (e.g. Buckminster, PDE, ALF, Corona, EMFT, ECF, Phoenix, etc), and other open source community resources (e.g. Apache Maven, Bugzilla, Php, contributed new technologies, Continuum, Eclipse Wiki, etc). The desire is to leverage as much of existing efforts as possible, avoid reimplementation and rework, and cooperatively use all available expertise and technology for Community Lifecycle Mangagement (you heard it hear first :).