Editing Eclipse integration
Warning: You are not logged in.
Your IP address will be recorded in this page's edit history.
Warning: This page is 32 kilobytes long; some browsers may have problems editing pages approaching or longer than 32kb. Please consider breaking the page into smaller sections.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 21: | Line 21: | ||
* With Prefinal release (week 37 middle of September) much improved support for Fremantle SDK development environment and new N900 device, improved support for Windows and Mac OS X as host PC, Mica plugin framework ready for third party plugin development, more automatic configuration of host PC for PC Connectivity using ZeroConf (Avahi) and DHCP, Samba support to enable disk mounts between Maemo device and Windows host PCs, Eclipse installation wizard for automated Maemo SDK Virtual Image installation, a lot of stability fixes for existing components and functionality. | * With Prefinal release (week 37 middle of September) much improved support for Fremantle SDK development environment and new N900 device, improved support for Windows and Mac OS X as host PC, Mica plugin framework ready for third party plugin development, more automatic configuration of host PC for PC Connectivity using ZeroConf (Avahi) and DHCP, Samba support to enable disk mounts between Maemo device and Windows host PCs, Eclipse installation wizard for automated Maemo SDK Virtual Image installation, a lot of stability fixes for existing components and functionality. | ||
- | === Maemo Eclipse Integration release versioning schema | + | === Maemo Eclipse Integration release versioning schema === |
- | Eclipse Integration project, version numbers | + | Eclipse Integration project, version numbers are composed of four (4) segments: 3 integers and a string respectively named major.minor.service.qualifier. The page <http://wiki.eclipse.org/Eclipse_Version_Numbering> describes guidelines for the first three segments, which relate to API promises in official supported releases. These rules do not apply to intermediate builds, however, so we will hold the major.minor.service segments at "2.0.0", indicating an API break from Eclipse Integration v1. |
Based on this, we will follow this convention in the whole version number: | Based on this, we will follow this convention in the whole version number: | ||
* "R<version>" indicates fully tested and stable official release, released according to the following schedule. | * "R<version>" indicates fully tested and stable official release, released according to the following schedule. | ||
+ | |||
* "<version>M or I or N" indicates that release is not fully tested official release but some prerelease. | * "<version>M or I or N" indicates that release is not fully tested official release but some prerelease. | ||
Line 33: | Line 34: | ||
* "M<number>" indicates milestones, which are integration tested and stable, released according to the following schedule. | * "M<number>" indicates milestones, which are integration tested and stable, released according to the following schedule. | ||
+ | |||
* "I<date>" indicates integration builds, which are developer tested, released every two weeks as sprint artifacts. | * "I<date>" indicates integration builds, which are developer tested, released every two weeks as sprint artifacts. | ||
+ | |||
* "N<date>", if used, indicates nightly builds, which are untested and unstable. | * "N<date>", if used, indicates nightly builds, which are untested and unstable. | ||
Learn more about Contributing to the wiki.