[jbosstools-issues] [JBoss JIRA] (JBIDE-22619) Decide strategy for fixversion targets in JIRA

[ https://issues.jboss.org/browse/JBIDE-22619?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22619: ------------------------------------ Purpose here as Max states is to make overhead less. We're now setting a fixversion AND a sprint #, which mean the same thing but require two steps / two labels. So why do we need both? And for JBDS issues, we also have a Target version (the GA release in which the JIRA will be done, even if fixed in an earlier milestone). So that's THREE places we're setting the same information. Then, when we move shortly to use jgit timestamps (JBIDE-13671), we eliminate the need for BUILD_ALIAS (for everything except the 2 plugins used to define the "version" of JBT/devstudio in ide-config.properties). So now the parent pom doesn't have to contain an Alpha/Beta quality-descriptor - we only care about WHEN it's being built, not HOW GOOD it is. Otherwise we will end up concocting arbitrary (and probably wrong) qualifiers like Alpha1, Alpha2, Alpha3 in JIRA just so as to differentiate between sprint releases. Does everyone remember when we were building toward Alpha3 and it was suddenly renamed to Final because we needed to make it a GA release ? Ah, good (confusing) times. -- This message was sent by Atlassian JIRA (v6.4.11#64026)