Max Rydahl Andersen [https://community.jboss.org/people/maxandersen] modified the document: "Tagging/branching of JBoss Tools Core subcomponents" To view the document, visit: https://community.jboss.org/docs/DOC-48350 -------------------------------------------------------------- Our recent move to git caused some confusion on how we tag/branch components in JBoss Tools core components. h1. Current Tag/Branching strategy To avoid future confusion here are the short version of the current approach: 1. Each component has its own version in manifest.mf/pom.xml 2. The git repositories should use tag/branches based on jbosstools version (jbosstools-<version>x for branches, jbosstools-<version> for tag) 3. In Jira use the jbosstools version for reporting/targeting issues. The advantage of the above is that git & jira use the same version. i.e. with a unified tag like "jbosstools-4.1.0.Alpha1" you can find which version is used of a specific component for a specific jboss tools release easily. This means from git you always know which branch/tag to checkout for a component to get matching version to a specific jboss tools core build/release. With Jira we would need to introduce a project for each individual component since Jira does not support version per components and thus jira queries for knowing current status of JBIDE suddenly gets very complex. h1. Discussion about improvements/future tagging can be found https://community.jboss.org/docs/DOC-48351 https://community.jboss.org/wiki/FutureStrategyForTaggingJBossToolsCore -------------------------------------------------------------- Comment by going to Community [https://community.jboss.org/docs/DOC-48350] Create a new document in JBoss Tools at Community [https://community.jboss.org/choose-container!input.jspa?contentType=102&a...]