]
Nick Boldt commented on JBIDE-24248:
------------------------------------
Documented here:
[~lhein] [~tim.moran] Comments welcome. If you see a problem with what's documented
(or feel it needs more fleshing out / automation / etc.) please reopen.
Document process for async Fuse Tools releases
----------------------------------------------
Key: JBIDE-24248
URL:
https://issues.jboss.org/browse/JBIDE-24248
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: fuse-tooling, updatesite
Affects Versions: 4.5.0.AM1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 4.5.0.AM2
Need to add a new devdoc explaining the release process for async Fuse Tooling releases.
See
https://github.com/jbdevstudio/jbdevstudio-devdoc/tree/master/release_gui...
Something like this, but with steps to update the composite*.xml files:
{quote}
If an async release is needed:
* any CI build can be chosen to be copied from /snapshots/ to /staging/ for QE review
& approval
* Once approved, that staged build can then be copied to /stable/ URL and can then be
linked from Central so users can discover the update.
* Thus
http://download.jboss.org/jbosstools/neon/stable/updates/compositeArtifac...
and
https://devstudio.redhat.com/10.0/stable/updates/compositeArtifacts.xml would simply
add in the new Fuse x.y.z release ... VERY MINIMAL effort to update these files (Nick or
Paul can both do this)
{quote}