[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-7737) Verify savara jobs

[ https://jira.jboss.org/browse/JBIDE-7737?page=com.atlassian.jira.plugin.s... ] Gary Brown commented on JBIDE-7737: ----------------------------------- One point - savara and jbosstools will have different release lifecycles. So I think it is best that jbosstools-savara have its own set of hudson jobs (as you now have setup) that reflect the lifecycle of jbosstools. As and when jbosstools need stable versions, branches/tags will be created. Similarly, savara (the separate non-Eclipse based distribution) will have its own release lifecycle, and therefore its own set of jobs. Occasionally, there will be unnecessary duplication (i.e. there will be two jobs building trunk currently). however it means that at any point, the jbosstools jobs can be updated to point to an appropriate branch/tag, without affecting the upstream aggregate job, or affecting the nornal savara distribution build. Keeping them all in the Savara view is good, as it enables them to be managed side by side. In general it would be good if Nick can manage the jbosstools-savara jobs, and I will manage the standard savara jobs. When approaching a release point, we then just need to decide whether a branch/tag needs to be setup for jbosstools. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira