https://sourceforge.net/p/chromedevtools/wiki/Versioning/Recent changes to VersioningenSat, 25 Apr 2015 13:43:52 -0000https://sourceforge.net/p/chromedevtools/wiki/Versioning/<div class="markdown_content"><h1 id="background">Background</h1> <p>As the ChromeDevTools project evolves, it is necessary to consistently keep track of each component version. </p> <p>Since the physical components are OSGi bundles developed using the Eclipse IDE, they will use the <a class="" href="http://wiki.eclipse.org/index.php/Version_Numbering" rel="nofollow">following</a> versioning scheme endorsed by the Eclipse developers. </p> <h1 id="component-versioning">Component Versioning</h1> <h2 id="chromedevtoolsprotocol"><a class="" href="/p/chromedevtools/wiki/ChromeDevToolsProtocol">ChromeDevToolsProtocol</a></h2> <p>The protocol version consists of two segments: </p> <div class="codehilite"><pre>major.minor </pre></div> <ul> <li>The "major" segment will change when the protocol is broken (e.g. the message format or existing command specifications are changed.) </li> <li>The "minor" segment will change in all other cases (e.g. new commands are added or unimplemented features are implemented.) </li> </ul> <h2 id="osgi-bundles">OSGi bundles</h2> <p>According to the referenced scheme, an OSGi bundle version identifier format is as following: </p> <div class="codehilite"><pre>major.minor.service.qualifier </pre></div> <p>A timestamp (YYYYMMDDHHmm) will be used as the "qualifier" segment for the plugins and features. </p> <h3 id="before-10-versioning-scheme">Before-1.0 versioning scheme</h3> <p>Major version number "0" indicates that SDK/Debugger haven't become stable enough. This milestone will be marked as "1.0" version. Until this happens, the temporary ("0.<code>*</code>") version scheme is used for all plugins and features. </p> <ul> <li>The "major" segment is 0. </li> <li>The "minor" segment will change when the SDK API is broken or there are major user-facing improvements. </li> <li>The "service" segment will change per release. The number is always even. </li> <li>The "qualifier" segment is automatically generated during every build. </li> </ul> <h3 id="planned-after-10-scheme">Planned after-1.0 scheme</h3> <h4 id="chromedevtoolssdk"><a class="" href="/p/chromedevtools/wiki/ChromeDevToolsSdk">ChromeDevToolsSdk</a></h4> <ul> <li>The "major" segment will change when the SDK API is broken. </li> <li>The "minor" segment will change when there are major improvements (not bugfixes) to the underlying implementation. </li> <li>The "service" segment will change when there are bugfixes. </li> <li>The "qualifier" segment is automatically generated during every build. </li> </ul> <h4 id="eclipsedebugger-plugins"><a class="" href="/p/chromedevtools/wiki/EclipseDebugger">EclipseDebugger</a> Plugins</h4> <ul> <li>The "major" segment will always be the same as that of the SDK version used. </li> <li>The "minor" segment will change when there are major user-facing improvements. </li> <li>The "service" segment will change when there are bugfixes. </li> <li>The "qualifier" segment is automatically generated during every build. </li> </ul> <h4 id="eclipsedebugger-and-chromedevtoolssdk-features"><a class="" href="/p/chromedevtools/wiki/EclipseDebugger">EclipseDebugger</a> and <a class="" href="/p/chromedevtools/wiki/ChromeDevToolsSdk">ChromeDevToolsSdk</a> Features</h4> <p>The feature versioning is consistent with these <a class="" href="http://wiki.eclipse.org/index.php/Version_Numbering#Versioning_features" rel="nofollow">Feature Versioning Guidelines</a>. </p></div>AnonymousSat, 25 Apr 2015 13:43:52 -0000https://sourceforge.net8550f923e5570e2134dd6814508bdc15a2baaf64