Bug 724111 (BRMS-54)

Summary: Need to track potentially separate UI and runtime versions for BRMS
Product: [JBoss] JBoss Enterprise BRMS Platform 5 Reporter: Len DiMaggio <ldimaggi>
Component: Documentation, Release Process, Configuration, Deployment, Patch Process, User InterfaceAssignee: trev <tkirby>
Status: CLOSED WONTFIX QA Contact:
Severity: unspecified Docs Contact:
Priority: high    
Version: 5.0.0 EA1   
Target Milestone: ---   
Target Release: future   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/BRMS-54
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-05-25 16:19:01 UTC Type: Task
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Len DiMaggio 2009-03-03 15:41:09 UTC 
Date of First Response: 2009-07-29 05:38:44

This topic came up during the March 3 SOA-P PM meeting - if we decouple the release schedule for the BRMS UI from the runtime, so that we can ship UI changes more quickly/often than we change the runtime, we will have to track separate version numbers - and display these numbers in the 'about' dialog.
Comment 1 trev 2009-07-29 09:38:44 UTC 
Decoupling will need to be driven via the project, moving out to 5.1. for 5.0.1 we will hardwire the relevant guvnor version into the pom in the brms platform branch
Comment 2 Jervis Liu 2010-09-13 04:11:44 UTC 
This wont happen in the near future.