[jbosstools-issues] [JBoss JIRA] (JBIDE-22355) JBT component CI build qualifiers still say Alpha1, but Alpha1 is released in JIRA and we're building toward Alpha2

[ https://issues.jboss.org/browse/JBIDE-22355?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22355: ------------------------------------ Sprint 114 ended May 24 [1]. So, all the bits built for that sprint will have a date stamp with 0519 or 0520 in them. Sprint 115 will end June 14. So, all the bits built for that sprint will have a date stamp likely around with 0609 or 0610 in them. Is that concrete enough or do you need me to dump a list of plugins and features from the last staged build [2] so you can see all the actual qualifiers? [1] https://issues.jboss.org/projects/JBIDE?selectedItem=com.atlassian.jira.j... [2] http://download.jboss.org/jbosstools/neon/staging/updates/core/4.4.0.Alpha2/ Note that for org.eclipse.wst.jsdt.nodejs.feature or org.eclipse.linuxtools.docker.feature there are no such Alpha/Beta/CR qualifiers. Just a datestamp. But we know they're from M7, so they're Beta quality. When we move up to the RC3/4 bits, we'll know they're CR/Final quality. There are other ways to know how good your bits are than simply by looking at the artifact jar file names. -- This message was sent by Atlassian JIRA (v6.4.11#64026)