[jbosstools-issues] [JBoss JIRA] (JBIDE-15252) Agree on a release URL for locus

[Nick Boldt (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-15252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nick Boldt resolved JBIDE-15252.
--------------------------------

      Assignee: Nick Boldt
    Resolution: Done


As per quorum, here are the new stabilized locations for Locus builds:

http://download.jboss.org/jbosstools/updates/integration/locus/ composite site
http://download.jboss.org/jbosstools/updates/integration/locus/ \{version1}
http://download.jboss.org/jbosstools/updates/integration/locus/ \{version2}
...
http://download.jboss.org/jbosstools/updates/development/locus/ composite site
http://download.jboss.org/jbosstools/updates/development/locus/ \{version1}
http://download.jboss.org/jbosstools/updates/development/locus/ \{version2}
...
http://download.jboss.org/jbosstools/updates/stable/locus/ composite site
http://download.jboss.org/jbosstools/updates/stable/locus/ \{version1}
http://download.jboss.org/jbosstools/updates/stable/locus/ \{version2}
...

Content will be published directly from this job [1] into /integration/locus/\{TARGET_FOLDER}/ per the job's configuration.

Content can then be published using this job [2] to copy from integration -> development or development -> stable.

[1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-locus.site_10/

[2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-promote/
                
> Agree on a release URL for locus
> --------------------------------
>
>                 Key: JBIDE-15252
>                 URL: https://issues.jboss.org/browse/JBIDE-15252
>             Project: Tools (JBoss Tools)
>          Issue Type: Task
>          Components: locus
>            Reporter: Mickael Istria
>            Assignee: Nick Boldt
>             Fix For: 1.0.0-LOCUS
>
>
> In order to make it release URL easy to remember and predictable, we need to agree on a pattern for Locus releases.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira