[jbosstools-issues] [JBoss JIRA] (JBDS-2046) Determine categories and feature groups in JBT/JBDS SOA Tooling's Central; determine categories in JBT/JBDS SOA Tooling's aggregate site

[ https://issues.jboss.org/browse/JBDS-2046?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBDS-2046: ----------------------------------------------- JBoss JIRA Server <jira-update(a)redhat.com&gt; made a comment on [bug 811977|https://bugzilla.redhat.com/show_bug.cgi?id=811977] Nick Boldt <nboldt(a)redhat.com&gt; made a comment on jira JBDS-2046 1. Declare when you want to code freeze for your first Beta release. Core is planning our code freeze THIS FRIDAY April 27. Maybe you want to piggy-back onto that? 2. Code freeze, and branch your code so you can build the upcoming release from a different set of bits from trunk. Build code from _stable_branch jobs instead of _trunk jobs. (Think "release" instead of "CI", if that helps.) 3. Publish aggregate site to devstudio.jboss.com. Add your discovery plugin to this file: https://devstudio.jboss.com/updates/5.0/devstudio-directory.xml. Note that doing this is scripted for ease of use: https://svn.jboss.org/repos/devstudio/trunk/documentation/Release_Guide/2... 4. Wait 30 mins for changes to wallace to replicate to devstudio.jboss.com 5. Fire up JBDS Beta2 (or later). Observe that JBoss Central now includes your two new connectors for SOA-P and BRMS. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira