Bug 724111 (BRMS-54) - Need to track potentially separate UI and runtime versions for BRMS
Summary: Need to track potentially separate UI and runtime versions for BRMS
Keywords:
Status: CLOSED WONTFIX
Alias: BRMS-54
Product: JBoss Enterprise BRMS Platform 5
Classification: JBoss
Component: Documentation, Release Process, Configuration, Deployment, Patch Process, User Interface
Version: 5.0.0 EA1
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: ---
: future
Assignee: trev
QA Contact:
URL: http://jira.jboss.org/jira/browse/BRM...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-03-03 15:41 UTC by Len DiMaggio
Modified: 2011-05-25 16:19 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-05-25 16:19:01 UTC
Type: Task

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker BRMS-54 0 None None None Never

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.
Note You need to log in before you can comment on or make changes to this bug.