[ https://issues.jboss.org/browse/JBIDE-15286?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-15286: --------------------------------------- it cannot be 1.2.2. There should be gap between current released version from 4.1.x stream and version in next dev stream, so we would be able to release update to 1.2.1 only. according to: {quote}When to change the service segment The service segment number must be incremented whenever there have been changes to a plug-in between releases that are not visible in its API. For example, a bug has been fixed in the code, the plug-in manifest has changed, documentation has changed, compiler settings have changed. In general, if that change happens in a service (a.k.a. maintenance) release, then 1 is added. If it happens for the next official release, 100 has to be added. As a result, the service segment number for official releases normally ends with a zero (0, 100, 200, etc.). If that is not true for whatever reason, then one must not add 100 but instead set the service segment number to the next number that is divisible by 100, so that the normal numbering scheme is restored. This practice makes it easy to manage one line of descent after a release and still guarantee that plug-ins coming in the next release will have a higher version number than ones from maintenance releases (thus enabling the usage of update manager from maintenance releases to the new releases).{quote} new version in dev N+1 stream should be 1.2.100. Then if we need deliver update for 4.1.0 as 4.1.1.Final usage would get updated version 1.2.2, which means this update could be installed only for 4.1.0.Final, but not for 4.2.0 stream where usage version is 1.2.100, because 1.2.1<1.2.2<1.2.100. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira