11:23 a.m.
Pre-release testing of rich:editor
----------------------------------
Key: RFPL-1633
URL: https://issues.jboss.org/browse/RFPL-1633
Project: RichFaces Planning
Issue Type: Task
Security Level: Public (Everyone can see)
Components: QE
Affects Versions: 4.1.0.Milestone2
Reporter: Lukáš Fryč
Assignee: Ján Jamrich
Fix For: 4.1.0.Milestone2
Editor has been greatly refactored in scope of M2 and it would be great to do release-wide
testing before end of M2, this includes:
* smoke testing of editor on all supported containers
* complete testing of all features of editor in all supported browsers
* smoke test with all available skins focusing on readability and usability in all
supported browsers
Please note your plan on testing matrix.
Changes that may affect testing:
* new 'richfaces' skin (made default)
** skin consistent with RichFaces component suite skins
** skinned main editor interface + popups
** popups should have consistent look with rich:popupPanel
* configuration through {{@config}} attribute or {{<f:facet
name="config">}}
* new attributes/facets ({{skin, config, lang, ondirty}})
[Complete list of fixed issues for editor in
M2|https://issues.jboss.org/secure/IssueNavigator.jspa?reset=true&jql...]
This testing should minimize the risk of introducing such fundamental changes in second
milestone.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:25 a.m.
New subject: [JBoss JIRA] Updated: (RFPL-1633) Pre-release testing of rich:editor
[
https://issues.jboss.org/browse/RFPL-1633?page=com.atlassian.jira.plugin....
]
Lukáš Fryč updated RFPL-1633:
-----------------------------
Description:
Editor has been greatly refactored in scope of M2 and it would be great to do release-wide
testing before end of M2, this includes:
* smoke testing of editor on all supported containers
* complete testing of all features of editor in all supported browsers
* smoke test with all available skins focusing on readability and usability in all
supported browsers
Please note your plan on testing matrix.
Changes that may affect testing:
* new 'richfaces' skin (made default)
** skin consistent with RichFaces component suite skins
** skinned main editor interface + popups
** popups should have consistent look with rich:popupPanel
* configuration through {{@config}} attribute or {{<f:facet
name="config">}}
* new attributes/facets ({{skin, config, lang, ondirty}})
[Complete list of fixed issues for editor in
M2|https://issues.jboss.org/secure/IssueNavigator.jspa?reset=true&jql...]
This testing should minimize the risk of introducing such fundamental changes in second
milestone.
was:
Editor has been greatly refactored in scope of M2 and it would be great to do release-wide
testing before end of M2, this includes:
* smoke testing of editor on all supported containers
* complete testing of all features of editor in all supported browsers
* smoke test with all available skins focusing on readability and usability in all
supported browsers
Please note your plan on testing matrix.
Changes that may affect testing:
* new 'richfaces' skin (made default)
** skin consistent with RichFaces component suite skins
** skinned main editor interface + popups
** popups should have consistent look with rich:popupPanel
* configuration through {{@config}} attribute or {{<f:facet
name="config">}}
* new attributes/facets ({{skin, config, lang, ondirty}})
[Complete list of fixed issues for editor in
M2|https://issues.jboss.org/secure/IssueNavigator.jspa?reset=true&jql...]
This testing should minimize the risk of introducing such fundamental changes in second
milestone.
Pre-release testing of rich:editor
----------------------------------
Key: RFPL-1633
URL: https://issues.jboss.org/browse/RFPL-1633
Project: RichFaces Planning
Issue Type: Task
Security Level: Public(Everyone can see)
Components: QE
Affects Versions: 4.1.0.Milestone2
Reporter: Lukáš Fryč
Assignee: Ján Jamrich
Fix For: 4.1.0.Milestone2
Editor has been greatly refactored in scope of M2 and it would be great to do
release-wide testing before end of M2, this includes:
* smoke testing of editor on all supported containers
* complete testing of all features of editor in all supported browsers
* smoke test with all available skins focusing on readability and usability in all
supported browsers
Please note your plan on testing matrix.
Changes that may affect testing:
* new 'richfaces' skin (made default)
** skin consistent with RichFaces component suite skins
** skinned main editor interface + popups
** popups should have consistent look with rich:popupPanel
* configuration through {{@config}} attribute or {{<f:facet
name="config">}}
* new attributes/facets ({{skin, config, lang, ondirty}})
[Complete list of fixed issues for editor in
M2|https://issues.jboss.org/secure/IssueNavigator.jspa?reset=true&jql...]
This testing should minimize the risk of introducing such fundamental changes in second
milestone.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:22 a.m.
New subject: [JBoss JIRA] Updated: (RFPL-1633) Pre-release testing of rich:editor
[
https://issues.jboss.org/browse/RFPL-1633?page=com.atlassian.jira.plugin....
]
Juraj Huska updated RFPL-1633:
------------------------------
Assignee: Juraj Huska (was: Ján Jamrich)
Pre-release testing of rich:editor
----------------------------------
Key: RFPL-1633
URL: https://issues.jboss.org/browse/RFPL-1633
Project: RichFaces Planning
Issue Type: Task
Security Level: Public(Everyone can see)
Components: QE
Affects Versions: 4.1.0.Milestone2
Reporter: Lukáš Fryč
Assignee: Juraj Huska
Fix For: 4.1.0.Milestone2
Editor has been greatly refactored in scope of M2 and it would be great to do
release-wide testing before end of M2, this includes:
* smoke testing of editor on all supported containers
* complete testing of all features of editor in all supported browsers
* smoke test with all available skins focusing on readability and usability in all
supported browsers
Please note your plan on testing matrix.
Changes that may affect testing:
* new 'richfaces' skin (made default)
** skin consistent with RichFaces component suite skins
** skinned main editor interface + popups
** popups should have consistent look with rich:popupPanel
* configuration through {{@config}} attribute or {{<f:facet
name="config">}}
* new attributes/facets ({{skin, config, lang, ondirty}})
[Complete list of fixed issues for editor in
M2|https://issues.jboss.org/secure/IssueNavigator.jspa?reset=true&jql...]
This testing should minimize the risk of introducing such fundamental changes in second
milestone.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:48 a.m.
New subject: [JBoss JIRA] Commented: (RFPL-1633) Pre-release testing of rich:editor
[
https://issues.jboss.org/browse/RFPL-1633?page=com.atlassian.jira.plugin....
]
Juraj Huska commented on RFPL-1633:
-----------------------------------
I am going to manually test editor in Metamer on this matrix configuration:
-containers: JBoss AS 6, JBoss AS 7
-browsers: FF 3.6.21, FF 7, Chrome 13, IE 8, IE 9
Pre-release testing of rich:editor
----------------------------------
Key: RFPL-1633
URL: https://issues.jboss.org/browse/RFPL-1633
Project: RichFaces Planning
Issue Type: Task
Security Level: Public(Everyone can see)
Components: QE
Affects Versions: 4.1.0.Milestone2
Reporter: Lukáš Fryč
Assignee: Juraj Huska
Fix For: 4.1.0.Milestone2
Editor has been greatly refactored in scope of M2 and it would be great to do
release-wide testing before end of M2, this includes:
* smoke testing of editor on all supported containers
* complete testing of all features of editor in all supported browsers
* smoke test with all available skins focusing on readability and usability in all
supported browsers
Please note your plan on testing matrix.
Changes that may affect testing:
* new 'richfaces' skin (made default)
** skin consistent with RichFaces component suite skins
** skinned main editor interface + popups
** popups should have consistent look with rich:popupPanel
* configuration through {{@config}} attribute or {{<f:facet
name="config">}}
* new attributes/facets ({{skin, config, lang, ondirty}})
[Complete list of fixed issues for editor in
M2|https://issues.jboss.org/secure/IssueNavigator.jspa?reset=true&jql...]
This testing should minimize the risk of introducing such fundamental changes in second
milestone.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:52 a.m.
New subject: [JBoss JIRA] Issue Comment Edited: (RFPL-1633) Pre-release testing of rich:editor
[
https://issues.jboss.org/browse/RFPL-1633?page=com.atlassian.jira.plugin....
]
Juraj Huska edited comment on RFPL-1633 at 9/6/11 4:50 AM:
-----------------------------------------------------------
I am going to manually test editor in Metamer on this matrix configuration:
-containers: JBoss AS 6, JBoss AS 7, Tomcat 6
-browsers: FF 3.6.21, FF 7, Chrome 13, IE 8, IE 9
was (Author: jhuska):
I am going to manually test editor in Metamer on this matrix configuration:
-containers: JBoss AS 6, JBoss AS 7
-browsers: FF 3.6.21, FF 7, Chrome 13, IE 8, IE 9
Pre-release testing of rich:editor
----------------------------------
Key: RFPL-1633
URL: https://issues.jboss.org/browse/RFPL-1633
Project: RichFaces Planning
Issue Type: Task
Security Level: Public(Everyone can see)
Components: QE
Affects Versions: 4.1.0.Milestone2
Reporter: Lukáš Fryč
Assignee: Juraj Huska
Fix For: 4.1.0.Milestone2
Editor has been greatly refactored in scope of M2 and it would be great to do
release-wide testing before end of M2, this includes:
* smoke testing of editor on all supported containers
* complete testing of all features of editor in all supported browsers
* smoke test with all available skins focusing on readability and usability in all
supported browsers
Please note your plan on testing matrix.
Changes that may affect testing:
* new 'richfaces' skin (made default)
** skin consistent with RichFaces component suite skins
** skinned main editor interface + popups
** popups should have consistent look with rich:popupPanel
* configuration through {{@config}} attribute or {{<f:facet
name="config">}}
* new attributes/facets ({{skin, config, lang, ondirty}})
[Complete list of fixed issues for editor in
M2|https://issues.jboss.org/secure/IssueNavigator.jspa?reset=true&jql...]
This testing should minimize the risk of introducing such fundamental changes in second
milestone.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:47 p.m.
New subject: [JBoss JIRA] Issue Comment Edited: (RFPL-1633) Pre-release testing of rich:editor
[
https://issues.jboss.org/browse/RFPL-1633?page=com.atlassian.jira.plugin....
]
Juraj Huska edited comment on RFPL-1633 at 9/6/11 9:47 AM:
-----------------------------------------------------------
I am going to manually test editor in Metamer on this matrix configuration:
-containers: JBoss AS 6, JBoss AS 7, Tomcat 6
-browsers: FF 3.6.21, FF 6(last stable), Chrome 13, IE 8, IE 9
was (Author: jhuska):
I am going to manually test editor in Metamer on this matrix configuration:
-containers: JBoss AS 6, JBoss AS 7, Tomcat 6
-browsers: FF 3.6.21, FF 7, Chrome 13, IE 8, IE 9
Pre-release testing of rich:editor
----------------------------------
Key: RFPL-1633
URL: https://issues.jboss.org/browse/RFPL-1633
Project: RichFaces Planning
Issue Type: Task
Security Level: Public(Everyone can see)
Components: QE
Affects Versions: 4.1.0.Milestone2
Reporter: Lukáš Fryč
Assignee: Juraj Huska
Fix For: 4.1.0.Milestone2
Editor has been greatly refactored in scope of M2 and it would be great to do
release-wide testing before end of M2, this includes:
* smoke testing of editor on all supported containers
* complete testing of all features of editor in all supported browsers
* smoke test with all available skins focusing on readability and usability in all
supported browsers
Please note your plan on testing matrix.
Changes that may affect testing:
* new 'richfaces' skin (made default)
** skin consistent with RichFaces component suite skins
** skinned main editor interface + popups
** popups should have consistent look with rich:popupPanel
* configuration through {{@config}} attribute or {{<f:facet
name="config">}}
* new attributes/facets ({{skin, config, lang, ondirty}})
[Complete list of fixed issues for editor in
M2|https://issues.jboss.org/secure/IssueNavigator.jspa?reset=true&jql...]
This testing should minimize the risk of introducing such fundamental changes in second
milestone.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:44 p.m.
New subject: [JBoss JIRA] Commented: (RFPL-1633) Pre-release testing of rich:editor
[
https://issues.jboss.org/browse/RFPL-1633?page=com.atlassian.jira.plugin....
]
Juraj Huska commented on RFPL-1633:
-----------------------------------
I have done this manual look and feel testing, with results which you can find in
attachment. I will have to review found problems with Lukas and then fire appropriate
JIRAs.
*Just the extract from summary:*
There are only minor issues, the most important issue is IMHO the issue with selects,
which does not provide other skinning than blueSky. Issues are not dependent on server
variety, only very little they are dependent on browser variety.
Pre-release testing of rich:editor
----------------------------------
Key: RFPL-1633
URL: https://issues.jboss.org/browse/RFPL-1633
Project: RichFaces Planning
Issue Type: Task
Security Level: Public(Everyone can see)
Components: QE
Affects Versions: 4.1.0.Milestone2
Reporter: Lukáš Fryč
Assignee: Juraj Huska
Fix For: 4.1.0.Milestone2
Attachments: editorIssues.odt
Editor has been greatly refactored in scope of M2 and it would be great to do
release-wide testing before end of M2, this includes:
* smoke testing of editor on all supported containers
* complete testing of all features of editor in all supported browsers
* smoke test with all available skins focusing on readability and usability in all
supported browsers
Please note your plan on testing matrix.
Changes that may affect testing:
* new 'richfaces' skin (made default)
** skin consistent with RichFaces component suite skins
** skinned main editor interface + popups
** popups should have consistent look with rich:popupPanel
* configuration through {{@config}} attribute or {{<f:facet
name="config">}}
* new attributes/facets ({{skin, config, lang, ondirty}})
[Complete list of fixed issues for editor in
M2|https://issues.jboss.org/secure/IssueNavigator.jspa?reset=true&jql...]
This testing should minimize the risk of introducing such fundamental changes in second
milestone.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:44 p.m.
New subject: [JBoss JIRA] Updated: (RFPL-1633) Pre-release testing of rich:editor
[
https://issues.jboss.org/browse/RFPL-1633?page=com.atlassian.jira.plugin....
]
Juraj Huska updated RFPL-1633:
------------------------------
Attachment: editorIssues.odt
Pre-release testing of rich:editor
----------------------------------
Key: RFPL-1633
URL: https://issues.jboss.org/browse/RFPL-1633
Project: RichFaces Planning
Issue Type: Task
Security Level: Public(Everyone can see)
Components: QE
Affects Versions: 4.1.0.Milestone2
Reporter: Lukáš Fryč
Assignee: Juraj Huska
Fix For: 4.1.0.Milestone2
Attachments: editorIssues.odt
Editor has been greatly refactored in scope of M2 and it would be great to do
release-wide testing before end of M2, this includes:
* smoke testing of editor on all supported containers
* complete testing of all features of editor in all supported browsers
* smoke test with all available skins focusing on readability and usability in all
supported browsers
Please note your plan on testing matrix.
Changes that may affect testing:
* new 'richfaces' skin (made default)
** skin consistent with RichFaces component suite skins
** skinned main editor interface + popups
** popups should have consistent look with rich:popupPanel
* configuration through {{@config}} attribute or {{<f:facet
name="config">}}
* new attributes/facets ({{skin, config, lang, ondirty}})
[Complete list of fixed issues for editor in
M2|https://issues.jboss.org/secure/IssueNavigator.jspa?reset=true&jql...]
This testing should minimize the risk of introducing such fundamental changes in second
milestone.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:44 p.m.
New subject: [JBoss JIRA] Issue Comment Edited: (RFPL-1633) Pre-release testing of rich:editor
[
https://issues.jboss.org/browse/RFPL-1633?page=com.atlassian.jira.plugin....
]
Juraj Huska edited comment on RFPL-1633 at 9/6/11 1:43 PM:
-----------------------------------------------------------
I am going to manually test editor in Metamer on this matrix configuration:
-containers: JBoss AS 6, Tomcat 6, Tomcat 7
-browsers: FF 3.6.21, FF 6(last stable), Chrome 13, IE 8, IE 9
was (Author: jhuska):
I am going to manually test editor in Metamer on this matrix configuration:
-containers: JBoss AS 6, JBoss AS 7, Tomcat 6
-browsers: FF 3.6.21, FF 6(last stable), Chrome 13, IE 8, IE 9
Pre-release testing of rich:editor
----------------------------------
Key: RFPL-1633
URL: https://issues.jboss.org/browse/RFPL-1633
Project: RichFaces Planning
Issue Type: Task
Security Level: Public(Everyone can see)
Components: QE
Affects Versions: 4.1.0.Milestone2
Reporter: Lukáš Fryč
Assignee: Juraj Huska
Fix For: 4.1.0.Milestone2
Attachments: editorIssues.odt
Editor has been greatly refactored in scope of M2 and it would be great to do
release-wide testing before end of M2, this includes:
* smoke testing of editor on all supported containers
* complete testing of all features of editor in all supported browsers
* smoke test with all available skins focusing on readability and usability in all
supported browsers
Please note your plan on testing matrix.
Changes that may affect testing:
* new 'richfaces' skin (made default)
** skin consistent with RichFaces component suite skins
** skinned main editor interface + popups
** popups should have consistent look with rich:popupPanel
* configuration through {{@config}} attribute or {{<f:facet
name="config">}}
* new attributes/facets ({{skin, config, lang, ondirty}})
[Complete list of fixed issues for editor in
M2|https://issues.jboss.org/secure/IssueNavigator.jspa?reset=true&jql...]
This testing should minimize the risk of introducing such fundamental changes in second
milestone.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:32 a.m.
New subject: [JBoss JIRA] Updated: (RFPL-1633) Pre-release testing of rich:editor
[
https://issues.jboss.org/browse/RFPL-1633?page=com.atlassian.jira.plugin....
]
Juraj Huska updated RFPL-1633:
------------------------------
Attachment: (was: editorIssues.odt)
Pre-release testing of rich:editor
----------------------------------
Key: RFPL-1633
URL: https://issues.jboss.org/browse/RFPL-1633
Project: RichFaces Planning
Issue Type: Task
Security Level: Public(Everyone can see)
Components: QE
Affects Versions: 4.1.0.Milestone2
Reporter: Lukáš Fryč
Assignee: Juraj Huska
Fix For: 4.1.0.Milestone2
Attachments: editorIssues.odt
Editor has been greatly refactored in scope of M2 and it would be great to do
release-wide testing before end of M2, this includes:
* smoke testing of editor on all supported containers
* complete testing of all features of editor in all supported browsers
* smoke test with all available skins focusing on readability and usability in all
supported browsers
Please note your plan on testing matrix.
Changes that may affect testing:
* new 'richfaces' skin (made default)
** skin consistent with RichFaces component suite skins
** skinned main editor interface + popups
** popups should have consistent look with rich:popupPanel
* configuration through {{@config}} attribute or {{<f:facet
name="config">}}
* new attributes/facets ({{skin, config, lang, ondirty}})
[Complete list of fixed issues for editor in
M2|https://issues.jboss.org/secure/IssueNavigator.jspa?reset=true&jql...]
This testing should minimize the risk of introducing such fundamental changes in second
milestone.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:32 a.m.
New subject: [JBoss JIRA] Updated: (RFPL-1633) Pre-release testing of rich:editor
[
https://issues.jboss.org/browse/RFPL-1633?page=com.atlassian.jira.plugin....
]
Juraj Huska updated RFPL-1633:
------------------------------
Attachment: editorIssues.odt
Edited issues with name of the screenshots included.
Pre-release testing of rich:editor
----------------------------------
Key: RFPL-1633
URL: https://issues.jboss.org/browse/RFPL-1633
Project: RichFaces Planning
Issue Type: Task
Security Level: Public(Everyone can see)
Components: QE
Affects Versions: 4.1.0.Milestone2
Reporter: Lukáš Fryč
Assignee: Juraj Huska
Fix For: 4.1.0.Milestone2
Attachments: editorIssues.odt
Editor has been greatly refactored in scope of M2 and it would be great to do
release-wide testing before end of M2, this includes:
* smoke testing of editor on all supported containers
* complete testing of all features of editor in all supported browsers
* smoke test with all available skins focusing on readability and usability in all
supported browsers
Please note your plan on testing matrix.
Changes that may affect testing:
* new 'richfaces' skin (made default)
** skin consistent with RichFaces component suite skins
** skinned main editor interface + popups
** popups should have consistent look with rich:popupPanel
* configuration through {{@config}} attribute or {{<f:facet
name="config">}}
* new attributes/facets ({{skin, config, lang, ondirty}})
[Complete list of fixed issues for editor in
M2|https://issues.jboss.org/secure/IssueNavigator.jspa?reset=true&jql...]
This testing should minimize the risk of introducing such fundamental changes in second
milestone.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:34 a.m.
New subject: [JBoss JIRA] Updated: (RFPL-1633) Pre-release testing of rich:editor
[
https://issues.jboss.org/browse/RFPL-1633?page=com.atlassian.jira.plugin....
]
Juraj Huska updated RFPL-1633:
------------------------------
Attachment: screenshots.zip
screenshots of issues
Pre-release testing of rich:editor
----------------------------------
Key: RFPL-1633
URL: https://issues.jboss.org/browse/RFPL-1633
Project: RichFaces Planning
Issue Type: Task
Security Level: Public(Everyone can see)
Components: QE
Affects Versions: 4.1.0.Milestone2
Reporter: Lukáš Fryč
Assignee: Juraj Huska
Fix For: 4.1.0.Milestone2
Attachments: editorIssues.odt, screenshots.zip
Editor has been greatly refactored in scope of M2 and it would be great to do
release-wide testing before end of M2, this includes:
* smoke testing of editor on all supported containers
* complete testing of all features of editor in all supported browsers
* smoke test with all available skins focusing on readability and usability in all
supported browsers
Please note your plan on testing matrix.
Changes that may affect testing:
* new 'richfaces' skin (made default)
** skin consistent with RichFaces component suite skins
** skinned main editor interface + popups
** popups should have consistent look with rich:popupPanel
* configuration through {{@config}} attribute or {{<f:facet
name="config">}}
* new attributes/facets ({{skin, config, lang, ondirty}})
[Complete list of fixed issues for editor in
M2|https://issues.jboss.org/secure/IssueNavigator.jspa?reset=true&jql...]
This testing should minimize the risk of introducing such fundamental changes in second
milestone.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:34 a.m.
New subject: [JBoss JIRA] Resolved: (RFPL-1633) Pre-release testing of rich:editor
[
https://issues.jboss.org/browse/RFPL-1633?page=com.atlassian.jira.plugin....
]
Juraj Huska resolved RFPL-1633.
-------------------------------
Resolution: Done
Pre-release testing of rich:editor
----------------------------------
Key: RFPL-1633
URL: https://issues.jboss.org/browse/RFPL-1633
Project: RichFaces Planning
Issue Type: Task
Security Level: Public(Everyone can see)
Components: QE
Affects Versions: 4.1.0.Milestone2
Reporter: Lukáš Fryč
Assignee: Juraj Huska
Fix For: 4.1.0.Milestone2
Attachments: editorIssues.odt, screenshots.zip
Editor has been greatly refactored in scope of M2 and it would be great to do
release-wide testing before end of M2, this includes:
* smoke testing of editor on all supported containers
* complete testing of all features of editor in all supported browsers
* smoke test with all available skins focusing on readability and usability in all
supported browsers
Please note your plan on testing matrix.
Changes that may affect testing:
* new 'richfaces' skin (made default)
** skin consistent with RichFaces component suite skins
** skinned main editor interface + popups
** popups should have consistent look with rich:popupPanel
* configuration through {{@config}} attribute or {{<f:facet
name="config">}}
* new attributes/facets ({{skin, config, lang, ondirty}})
[Complete list of fixed issues for editor in
M2|https://issues.jboss.org/secure/IssueNavigator.jspa?reset=true&jql...]
This testing should minimize the risk of introducing such fundamental changes in second
milestone.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4677
days inactive
4679
days old
richfaces-planning-issues@lists.jboss.org
12 comments
2 participants
participants (2)
-
Juraj Huska (JIRA) -
Lukáš Fryč (JIRA)