[
https://issues.jboss.org/browse/JBIDE-22355?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-22355:
---------------------------------------------
I have a really hard time following your logic. Can you give examples on a timeline
instead ? I'm not really grokking what is new/different in your explanation/thought
experiment.
one thing though: saying being agile = always final is really not applicable for us since
we do not control the full stack nor can we (unless we start having mulitple parallel
branches across the component tree) always be final in the sense of osgi versioning.
JBT component CI build qualifiers still say Alpha1, but Alpha1 is
released in JIRA and we're building toward Alpha2
-------------------------------------------------------------------------------------------------------------------
Key: JBIDE-22355
URL:
https://issues.jboss.org/browse/JBIDE-22355
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: build
Reporter: Mickael Istria
Assignee: Nick Boldt
Priority: Critical
Fix For: 4.4.0.Alpha2
Build qualifiers, parent pom version, and version of parent pom referenced by components
are still Alpha1.
All those should be moved to Alpha2 (they should be moved just when branching/releasing
actually)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)