Bug 792990 (JBEPP-70)

Summary:	Change Portal version from 4.3.0-SP1 to 4.3.0-CP1
Product:	[JBoss] JBoss Enterprise Portal Platform 4	Reporter:	Joao Viragine <joao.viragine>
Component:	Portal	Assignee:	Default User <jbpapp-maint>
Status:	CLOSED NEXTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	4.3.0.GA_CP1	CC:	epp-bugs, joao.viragine
Target Milestone:	---
Target Release:	4.3.0.GA_CP2
Hardware:	Unspecified
OS:	Unspecified
URL:	http://jira.jboss.org/jira/browse/JBEPP-70
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:	EPP 4.3 CP01
Last Closed:	2009-07-22 10:08:35 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 Joao Viragine 2009-05-01 14:26:16 UTC

Date of First Response: 2009-05-04 03:09:59
project_key: JBEPP

PortalConstants uses: Version.Qualifier.Prefix.SNAPSHOT

AFAIK, SP1 should be CP1 or even better: CP01

This may confuse our customer.

Comment 1 Thomas Heute 2009-05-04 07:09:59 UTC

It's using Version.Qualifier.Prefix.SP == Service Pach (which is equivalent to Cummulative patch).

The reason why it was not showing CP is that CP didn't exist and we would have had to reissue a new versoin of the common module very late in the process :-/

Agreed though that for next time we should change to CP, Jira will help to remember

Comment 2 Thomas Heute 2009-07-22 10:08:35 UTC

Next release will show CP02