[jbosstools-issues] [JBoss JIRA] (JBIDE-22355) Build qualifier still say Alpha2

[ https://issues.jboss.org/browse/JBIDE-22355?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-22355 at 5/16/16 11:24 AM: -------------------------------------------------------------- This was intentional. I wanted to see if we could survive NOT churning the parent pom & root poms for JBT 4.4 / DS 10. You may have noticed we did create 4.4.0.Alpha1x branches - we simply staged the latest CI build from master. Way faster! We need to discuss how to handle this, because going forward, I think we should only have to bump root poms and parent pom versions when something in parent pom ACTUALLY CHANGES. ([~maxandersen] has been asking for this for 2+ years. Time to become more CI/CD capable.) * Should the Alpha2 qualifier appear as a -DBUILD_ALIAS=Alpha2 override in Jenkins, and thus dev's local builds will still use Alpha1 (and therefore be considered "older" even when the timestamp is newer) ? Or should we move the alias to AFTER the date/timestamp (as it used to be) so that the determinant for "what is new" becomes the date/timestamp, rather than the subjective quality descriptor? * Should we only use the Alpha2 qualifier on JBT and DS folders/zips which are staged for QE, and thus all component bits will stay Alpha1 until we declare we're ready to move up to Beta, CR, or Final? In this case, there's no need to reorder qualifiers to put date/timestamp BEFORE the BUILD_ALIAS. And we would still need to bump parent pom once in a while, but ONLY when it's time to move to a more "stable quality" descriptor. * What if we drop the qualifier entirely from all the component builds, and only retain it as part of the JBT/DS productization process? was (Author: nickboldt): This was intentional. I wanted to see if we could survive NOT churning the parent pom & root poms for JBT 4.4 / DS 10. We need to discuss how to handle this, because going forward, I think we should only have to bump root poms and parent pom versions when something in parent pom ACTUALLY CHANGES. ([~maxandersen] has been asking for this for 2+ years. Time to become more CI/CD capable.) * Should the Alpha2 qualifier appear as a -DBUILD_ALIAS=Alpha2 override in Jenkins, and thus dev's local builds will still use Alpha1 (and therefore be considered "older" even when the timestamp is newer) ? Or should we move the alias to AFTER the date/timestamp (as it used to be) so that the determinant for "what is new" becomes the date/timestamp, rather than the subjective quality descriptor? * Should we only use the Alpha2 qualifier on JBT and DS folders/zips which are staged for QE, and thus all component bits will stay Alpha1 until we declare we're ready to move up to Beta, CR, or Final? In this case, there's no need to reorder qualifiers to put date/timestamp BEFORE the BUILD_ALIAS. And we would still need to bump parent pom once in a while, but ONLY when it's time to move to a more "stable quality" descriptor. * What if we drop the qualifier entirely from all the component builds, and only retain it as part of the JBT/DS productization process? -- This message was sent by Atlassian JIRA (v6.4.11#64026)