[
http://jira.jboss.com/jira/browse/JBPORTAL-1203?page=comments#action_1235... ]
Chris Laprun commented on JBPORTAL-1203:
----------------------------------------
I'd add: run through a couple of scenarios in the GUI as well to make sure that we
don't overlook anything major. For example, with WSRP, we need now (again after the
fix for the deployment issue) to actively do something with a consumer before we know that
it correctly works. One such example would be to log in as admin and try to access the
portlets for all the available portlet invokers (and make sure that all the invokers that
are supposed to be there indeed are).
Portal release steps issue
--------------------------
Key: JBPORTAL-1203
URL:
http://jira.jboss.com/jira/browse/JBPORTAL-1203
Project: JBoss Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Portal Test
Affects Versions: 2.6.Alpha1
Reporter: Prabhat Jha
Assigned To: Prabhat Jha
Priority: Critical
Fix For: 2.6.Beta1
The detail of the problem is described at
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4002954#....
We need to add to the release process the following:
1. Check that JBossAS bundled with portal starts properly.
2. Deploy the jboss-portal.sar built using ant -f distro.xm to a running instance of
JBossAS and make sure that deployment goes fine.
3. Download the prebuilt binaries from sourceforge, deploy jboss-portal.sar and make sure
deployment goes without any error.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira