[
https://issues.jboss.org/browse/JBIDE-18833?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-18833:
---------------------------------------------
It should point to what eventually be the next thing we are testing/developing to land in
staging for this release train.
If there are multiple branches active then I can't think of one case where not one of
them is what we are testing. Also I can't recall when we ever had more than one branch
for one release train.
And if we do - then sure, then one of them is the next and the others "special
cases" which for those involved will be aware of where the out will be put.
But for 99.999% of our usage outside ci builds these vanity urls are what we have and are
posting for simple ease of use and least surprises. That is at least the intention but for
some reason every new release train we expose our internal naming uneccessarily.
luna nightly are not being updated preventing QE to do easy testing
of committed code
-------------------------------------------------------------------------------------
Key: JBIDE-18833
URL:
https://issues.jboss.org/browse/JBIDE-18833
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: build
Reporter: Max Rydahl Andersen
Assignee: Nick Boldt
Priority: Blocker
Fix For: 4.2.1.Final
http://download.jboss.org/jbosstools/updates/nightly/luna/ composite*.xml was updated
26-nov but latest build there is from 28-oct-2014 (29 days ago)
I could not spot updates in
https://github.com/jbdevstudio/jbdevstudio-ci related to
this.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)