Skip to main content
Jump to: navigation, search

Difference between revisions of "ECF/Ganymede Roadmap"

< ECF
(API Compatibility)
 
(31 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 +
This page is the [[Eclipse Communication Framework]]'s roadmap for the [[Ganymede Simultaneous Release]].
 +
 
==API Compatibility==
 
==API Compatibility==
  
As a goal, backward compatibility will be maintained at least until the ECF major release (i.e. 2.0.0).  This will allow old applications to run on new API until the next major release/Ganymede.  If we find that we must break backward compatibility for some reason prior to 2.0.0 then we will do so on a *minor release* only.
+
As a goal, backward compatibility will be maintained at least until the ECF major release (i.e. 2.0.0).  This will allow old applications to run on top of any new API until the next major release/Ganymede.  If we find that we must break backward compatibility for some reason prior to 2.0.0 then we will do so on a '''minor release''' only.
  
 
==API Additions==
 
==API Additions==
  
API additions will generally take place only with minor releases (i.e. Y in 1.Y.0 version numbers).  The current expectation is that in Ganymede, such minor releases will occur *approximately every 2 months* until Ganymede release train begins, and then correspond to milestone releases for Ganymede (every six weeks from Dec 2007-May 2008).
+
API additions will generally take place only with minor releases (i.e. Y in 1.Y.0 version numbers).  The current expectation is that in Ganymede, such minor releases will occur '''approximately every 2 months''' until the Ganymede release train begins, and then correspond to milestone releases for Ganymede (every six weeks from Dec 2007-May 2008).
  
 
==Version Numbering==
 
==Version Numbering==
Line 13: Line 15:
 
ECF will have several maintenance releases for the ECF 1.0 stream (and all other releases).  The number of these maintenance releases will be determined by the number of bugs identified after each release.  These maintenance releases will be limited to bug fixes and will not generally include externally visible API changes.   
 
ECF will have several maintenance releases for the ECF 1.0 stream (and all other releases).  The number of these maintenance releases will be determined by the number of bugs identified after each release.  These maintenance releases will be limited to bug fixes and will not generally include externally visible API changes.   
  
ECF's maintenance releases will follow the conventions described in [[Version Numbering]].  Specifically, the service segment (i.e. Z in 1.0.Z.v20070625) will change by increments of 100 for each maintenance release e.g. 1.0.100 for first maintenance release, 1.0.200 for second, etc. Also see [[Version Numbering#Overall_example]].
+
ECF's maintenance releases will follow the conventions described in [[Version Numbering]].  Specifically, the service segment (i.e. Z in 1.0.Z.v20070625) will change by increments of 100 for each maintenance release e.g. 1.0.100 for first maintenance release, 1.0.200 for second, etc. See the [[Version Numbering#Overall example|overall example]] of the version numbering scheme for further details.
  
When *backward compatible* API changes occur (e.g. API additions), this will result in a change to the minor segment (e.g. Y in 1.Y.0.v20050507).  ECF will attempt to schedule such minor releases approximately every 2 months until the Ganymede milestone releases begin (~Dec 2007), and once they do start, then synchronize minor releases with milestone releases (approximately 6 weeks apart).
+
When '''backward compatible''' API changes occur (e.g. API additions), this will result in a change to the minor segment (e.g. Y in 1.Y.0.v20050507).  ECF will attempt to schedule such minor releases approximately every 2 months until the Ganymede milestone releases begin (~Dec 2007), and once they do start, then synchronize minor releases with milestone releases (approximately 6 weeks apart).
  
 
Minor releases will also contain feature additions and UI changes/enhancements.   
 
Minor releases will also contain feature additions and UI changes/enhancements.   
  
ECF will have a major segment changes (i.e. X in X.0.0.A) with *potentially backward compatibility breaking* changes.  The current expectation is that these will occur every year as part of the simultaneous release (i.e. 2.0.0) and subsequent simultaneous releases.  If project conditions changes occur (i.e. more resources), it's possible that major releases can/would occur more frequently.
+
ECF will have a major segment changes (i.e. X in X.0.0.A) with '''potentially backward compatibility breaking''' changes.  The current expectation is that these will occur every year as part of the simultaneous release (i.e. 2.0.0) and subsequent simultaneous releases.  If project conditions changes occur (i.e. more resources), it is possible that major releases can/would occur more frequently.
  
 
ECF will also begin having an automated build, allowing both developers and others to work with daily integration builds if they so choose.
 
ECF will also begin having an automated build, allowing both developers and others to work with daily integration builds if they so choose.
Line 27: Line 29:
 
1-per day via ECF automated build.
 
1-per day via ECF automated build.
 
===Maintenance Releases===
 
===Maintenance Releases===
*1.0.1 (Target: Friday, July 13th, 2007)
+
*1.0.1 Target: Friday, July 13th, 2007, Actual: Saturday, July 14th, 2007.
**[https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Technology&product=ECF&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&resolution=FIXED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2007-06-29&chfieldto=2007-07-13&chfield=resolution&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Bugs fixed]
+
*1.0.2 Target: Friday, Aug 3, 2007, Actual: Friday, Aug 3, 2007.
*1.0.2 (Target: Friday, July 27th, 2007)
+
*1.0.3 Actual: Thursday, Sept 27, 2007.
**[https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Technology&product=ECF&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&resolution=FIXED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2007-07-13&chfieldto=2007-07-27&chfield=resolution&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Bugs fixed]
+
 
 
===Minor Releases===
 
===Minor Releases===
*1.1.0 (Target: Friday, Aug 17th, 2007)
+
*1.2.0 Target: Friday, Oct 19th, 2007, Actual: Friday, Oct 19, 2007.  Click [http://www.eclipse.org/ecf/downloads.php here to download]
*1.2.0 (Target: Friday, Oct 5th, 2007)
+
**[https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Technology&product=ECF&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&resolution=FIXED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2007-06-25&chfieldto=2007-10-19&chfield=resolution&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Bugs Fixed]
*1.3.0 (Target: Friday, Nov 23rd, 2007)
+
*2.0.0M4 (Target: Ganymede M4 - Dec 14, 2007)
*1.4.0 (Target: Ganymede M4 - mid Dec, 2007)
+
*2.0.0M5 (Target: Ganymede M5 - early Feb, 2008)
*1.5.0 (Target: Ganymede M5 - early Feb, 2008)
+
*2.0.0M6 (Target: Ganymede M6 - mid March/EclipseCon 2008)
*1.6.0 (Target: Ganymede M6 - mid March/EclipseCon 2008)
+
*2.0.0M7 (Target: Ganymede M7 - early May, 2008)
*1.7.0 (Target: Ganymede M7 - early May, 2008)
+
*2.0.0RC1 (Target: Ganymede RC1 - late May, 2008)
*1.8.0 (Target: Ganymede RC1 - late May, 2008)
+
*2.0.0RC4 (Target: Ganymede RC4 - early June, 2008)
*1.9.0 (Target: Ganymede RC4 - early June, 2008)
+
 
 
===Major Releases===
 
===Major Releases===
 
*ECF 2.0.0/Ganymede (Target: Late June, 2008)
 
*ECF 2.0.0/Ganymede (Target: Late June, 2008)
 
[[Category:Eclipse Communication Framework]]
 
[[Category:Eclipse Communication Framework]]
 +
 +
==Development Themes==
 +
Some development themes (in no particular order for time being)
 +
===Voice Over IP===
 +
*Jingle
 +
*SIP
 +
*IAX/Asterisk
 +
===UI for Chat/IM/Contacts List===
 +
 +
Bugs
 +
 +
===UI Extensibility===
 +
===Platform Ready===
 +
*Equinox Provisioning/File Transfer
 +
*Equinox JAAS Integration
 +
 +
===Shared Editing===
 +
*Cola ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=170866 Bug 170866], [https://dev.eclipse.org/ipzilla/show_bug.cgi?id=1558 CQ 1558])
 +
*XCDE
 +
===RCP/eRCP Applications===
 +
*Sudoku/Games
 +
===Servers===
 +
*Generic Server
 +
*JMS Servers
 +
*Others
 +
===Integration (Mylyn/Corona/Others)===
 +
*[[Mylyn synchronous context sharing, based on Mylyn and ECF integration|Mylyn synchronous context sharing]]
 +
* VNC
 +
*RSSOwl
 +
===New Providers and Existing Provider Improvement===
 +
*Sametime ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=146954 Bug 146954])
 +
*AIM ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=146646 Bug 146646])
 +
*Yahoo ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=146955 Bug 146955], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=148854 Bug 148854])
 +
*Service Discovery (OSGi discovery, JXTA, Jini, UPnP, etc)
 +
*JMS providers
 +
 +
{{ECF}}
 +
 +
[[Category:Eclipse Communication Framework]]
 +
[[Category:ECF]]

Latest revision as of 09:23, 22 December 2010

This page is the Eclipse Communication Framework's roadmap for the Ganymede Simultaneous Release.

API Compatibility

As a goal, backward compatibility will be maintained at least until the ECF major release (i.e. 2.0.0). This will allow old applications to run on top of any new API until the next major release/Ganymede. If we find that we must break backward compatibility for some reason prior to 2.0.0 then we will do so on a minor release only.

API Additions

API additions will generally take place only with minor releases (i.e. Y in 1.Y.0 version numbers). The current expectation is that in Ganymede, such minor releases will occur approximately every 2 months until the Ganymede release train begins, and then correspond to milestone releases for Ganymede (every six weeks from Dec 2007-May 2008).

Version Numbering

In general, ECF will follow the version numbering described in Version Numbering for Europa Simultaneous Release.

ECF will have several maintenance releases for the ECF 1.0 stream (and all other releases). The number of these maintenance releases will be determined by the number of bugs identified after each release. These maintenance releases will be limited to bug fixes and will not generally include externally visible API changes.

ECF's maintenance releases will follow the conventions described in Version Numbering. Specifically, the service segment (i.e. Z in 1.0.Z.v20070625) will change by increments of 100 for each maintenance release e.g. 1.0.100 for first maintenance release, 1.0.200 for second, etc. See the overall example of the version numbering scheme for further details.

When backward compatible API changes occur (e.g. API additions), this will result in a change to the minor segment (e.g. Y in 1.Y.0.v20050507). ECF will attempt to schedule such minor releases approximately every 2 months until the Ganymede milestone releases begin (~Dec 2007), and once they do start, then synchronize minor releases with milestone releases (approximately 6 weeks apart).

Minor releases will also contain feature additions and UI changes/enhancements.

ECF will have a major segment changes (i.e. X in X.0.0.A) with potentially backward compatibility breaking changes. The current expectation is that these will occur every year as part of the simultaneous release (i.e. 2.0.0) and subsequent simultaneous releases. If project conditions changes occur (i.e. more resources), it is possible that major releases can/would occur more frequently.

ECF will also begin having an automated build, allowing both developers and others to work with daily integration builds if they so choose.

Release Dates

Development Builds

1-per day via ECF automated build.

Maintenance Releases

  • 1.0.1 Target: Friday, July 13th, 2007, Actual: Saturday, July 14th, 2007.
  • 1.0.2 Target: Friday, Aug 3, 2007, Actual: Friday, Aug 3, 2007.
  • 1.0.3 Actual: Thursday, Sept 27, 2007.

Minor Releases

  • 1.2.0 Target: Friday, Oct 19th, 2007, Actual: Friday, Oct 19, 2007. Click here to download
  • 2.0.0M4 (Target: Ganymede M4 - Dec 14, 2007)
  • 2.0.0M5 (Target: Ganymede M5 - early Feb, 2008)
  • 2.0.0M6 (Target: Ganymede M6 - mid March/EclipseCon 2008)
  • 2.0.0M7 (Target: Ganymede M7 - early May, 2008)
  • 2.0.0RC1 (Target: Ganymede RC1 - late May, 2008)
  • 2.0.0RC4 (Target: Ganymede RC4 - early June, 2008)

Major Releases

  • ECF 2.0.0/Ganymede (Target: Late June, 2008)

Development Themes

Some development themes (in no particular order for time being)

Voice Over IP

  • Jingle
  • SIP
  • IAX/Asterisk

UI for Chat/IM/Contacts List

Bugs

UI Extensibility

Platform Ready

  • Equinox Provisioning/File Transfer
  • Equinox JAAS Integration

Shared Editing

RCP/eRCP Applications

  • Sudoku/Games

Servers

  • Generic Server
  • JMS Servers
  • Others

Integration (Mylyn/Corona/Others)

New Providers and Existing Provider Improvement

Eclipse Communication Framework
API
API DocumentationJavadocProviders
Development
Development GuidelinesIntegrators Guide

Back to the top