August 2009 - richfaces-planning-issues

[JBoss JIRA] Assigned: (RFPL-70) automate RF Demo app testing with IE8

by Prabhat Jha (JIRA)

[ https://jira.jboss.org/jira/browse/RFPL-70?page=com.atlassian.jira.plugin... ] Prabhat Jha reassigned RFPL-70: ------------------------------- Assignee: Lukas Fryc (was: Pavol Pitonak) > automate RF Demo app testing with IE8 > ------------------------------------- > > Key: RFPL-70 > URL: https://jira.jboss.org/jira/browse/RFPL-70 > Project: RichFaces Planning > Issue Type: Sub-task > Reporter: Prabhat Jha > Assignee: Lukas Fryc > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 4 months

1
0
0 / 0

[JBoss JIRA] Resolved: (RFPL-66) Renderer template compiler unit tests

by Andrey Markhel (JIRA)

[ https://jira.jboss.org/jira/browse/RFPL-66?page=com.atlassian.jira.plugin... ] Andrey Markhel resolved RFPL-66. -------------------------------- Resolution: Done Assignee: Nick Belaevski (was: Andrey Markhel) Done > Renderer template compiler unit tests > ------------------------------------- > > Key: RFPL-66 > URL: https://jira.jboss.org/jira/browse/RFPL-66 > Project: RichFaces Planning > Issue Type: Task > Components: CDK > Affects Versions: 4.0.0.ALPHA1 > Reporter: Nick Belaevski > Assignee: Nick Belaevski > Fix For: 4.0.0.ALPHA1 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 4 months

1
0
0 / 0

[JBoss JIRA] Updated: (RFPL-82) Create an updated copyright header for all new/modfied/copied files for the project

by Jay Balunas (JIRA)

[ https://jira.jboss.org/jira/browse/RFPL-82?page=com.atlassian.jira.plugin... ] Jay Balunas updated RFPL-82: ---------------------------- Fix Version/s: 4.0.0.ALPHA2 (was: 4.0.0.ALPHA1) Affects Version/s: 3.3.2.CR1 (was: 3.3.2.GA) > Create an updated copyright header for all new/modfied/copied files for the project > ----------------------------------------------------------------------------------- > > Key: RFPL-82 > URL: https://jira.jboss.org/jira/browse/RFPL-82 > Project: RichFaces Planning > Issue Type: Task > Components: administration, site, svn > Affects Versions: 3.3.2.CR1, 4.0.0.ALPHA1 > Reporter: Jay Balunas > Assignee: Jay Balunas > Priority: Critical > Fix For: 3.3.2.GA, 4.0.0.ALPHA2 > > > Something similar to http://seamframework.org/Community/SeamLicensing with RichFaces specific items and phrasing. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 4 months

1
0
0 / 0

[JBoss JIRA] Resolved: (RFPL-77) Update 3.3.X doc release procedure wiki page with latest steps for docs.jboss.org

by Svetlana mukhina (JIRA)

[ https://jira.jboss.org/jira/browse/RFPL-77?page=com.atlassian.jira.plugin... ] Svetlana mukhina resolved RFPL-77. ---------------------------------- Resolution: Done done > Update 3.3.X doc release procedure wiki page with latest steps for docs.jboss.org > --------------------------------------------------------------------------------- > > Key: RFPL-77 > URL: https://jira.jboss.org/jira/browse/RFPL-77 > Project: RichFaces Planning > Issue Type: Task > Components: administration, build, docs, site > Affects Versions: Site > Reporter: Jay Balunas > Assignee: Svetlana mukhina > Fix For: Site > > > The release procedures need to be updated for docs on the wiki page: http://www.jboss.org/community/wiki/RichFaces33xReleaseProcedure -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 4 months

1
0
0 / 0

[JBoss JIRA] Commented: (RFPL-78) Update 3.3.X release procedure based on comments from team meeting

by Konstantin Mishin (JIRA)

[ https://jira.jboss.org/jira/browse/RFPL-78?page=com.atlassian.jira.plugin... ] Konstantin Mishin commented on RFPL-78: --------------------------------------- #14 - We should just commit in repository.jboss.org/maven2. #16 - It should be done for GA version only. I have added small corrections to this point. > Update 3.3.X release procedure based on comments from team meeting > ------------------------------------------------------------------ > > Key: RFPL-78 > URL: https://jira.jboss.org/jira/browse/RFPL-78 > Project: RichFaces Planning > Issue Type: Task > Components: administration, build, site > Affects Versions: Site > Reporter: Jay Balunas > Assignee: Jay Balunas > Priority: Critical > Fix For: 3.3.2.CR1, Site > > Attachments: 8-18-2009-rf-team-meeting-transcript.rtf > > > From Meeting minutes - http://www.jboss.org/community/wiki/RichFacesTeamMeetingMinutes8-18-2009 > Wiki: http://www.jboss.org/community/wiki/RichFaces33xReleaseProcedure > * item 15 needs to be updated > * Don't need to update demos except for GA > * Expand "When QE/Dev ready - release" > o Need steps and details > o Upload to downloads.jboss.org and others ( see attached transcript) > * Magnolia site update requirements > * Listing of all places that need updated ( wikipedia, twitter, blog, etc...) > This will involve Konstantin as well -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 4 months

1
0
0 / 0

[JBoss JIRA] Commented: (RFPL-78) Update 3.3.X release procedure based on comments from team meeting

by Jay Balunas (JIRA)

[ https://jira.jboss.org/jira/browse/RFPL-78?page=com.atlassian.jira.plugin... ] Jay Balunas commented on RFPL-78: --------------------------------- #14 - we still need more details for this - what steps are needed to follow to upload to maven, or jboss.org? #16 - Even for a CR1, or ALPHA the version needs to be updated to the next planned release correct? #17 - magnolia project site update - we need to create an internal wiki page with credentials and various other internal project information. I'll create a jira for it. #17.5 - The docs page should point to the "latest_3_3_X" ( and 4.0 in future ) so that we don't need to updates links. Same with nightly - they will be build and uploaded to the same location every night and so the links should not need to be updated. The only time docs should be updated is for new major versions like 4.0. > Update 3.3.X release procedure based on comments from team meeting > ------------------------------------------------------------------ > > Key: RFPL-78 > URL: https://jira.jboss.org/jira/browse/RFPL-78 > Project: RichFaces Planning > Issue Type: Task > Components: administration, build, site > Affects Versions: Site > Reporter: Jay Balunas > Assignee: Jay Balunas > Priority: Critical > Fix For: 3.3.2.CR1, Site > > Attachments: 8-18-2009-rf-team-meeting-transcript.rtf > > > From Meeting minutes - http://www.jboss.org/community/wiki/RichFacesTeamMeetingMinutes8-18-2009 > Wiki: http://www.jboss.org/community/wiki/RichFaces33xReleaseProcedure > * item 15 needs to be updated > * Don't need to update demos except for GA > * Expand "When QE/Dev ready - release" > o Need steps and details > o Upload to downloads.jboss.org and others ( see attached transcript) > * Magnolia site update requirements > * Listing of all places that need updated ( wikipedia, twitter, blog, etc...) > This will involve Konstantin as well -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 4 months

1
0
0 / 0

[JBoss JIRA] Updated: (RFPL-78) Update 3.3.X release procedure based on comments from team meeting

by Jay Balunas (JIRA)

[ https://jira.jboss.org/jira/browse/RFPL-78?page=com.atlassian.jira.plugin... ] Jay Balunas updated RFPL-78: ---------------------------- Description: >From Meeting minutes - http://www.jboss.org/community/wiki/RichFacesTeamMeetingMinutes8-18-2009 Wiki: http://www.jboss.org/community/wiki/RichFaces33xReleaseProcedure * item 15 needs to be updated * Don't need to update demos except for GA * Expand "When QE/Dev ready - release" o Need steps and details o Upload to downloads.jboss.org and others ( see attached transcript) * Magnolia site update requirements * Listing of all places that need updated ( wikipedia, twitter, blog, etc...) This will involve Konstantin as well was: >From Meeting minutes - http://www.jboss.org/community/wiki/RichFacesTeamMeetingMinutes8-18-2009 * item 15 needs to be updated * Don't need to update demos except for GA * Expand "When QE/Dev ready - release" o Need steps and details o Upload to downloads.jboss.org and others ( see attached transcript) * Magnolia site update requirements * Listing of all places that need updated ( wikipedia, twitter, blog, etc...) This will involve Konstantin as well > Update 3.3.X release procedure based on comments from team meeting > ------------------------------------------------------------------ > > Key: RFPL-78 > URL: https://jira.jboss.org/jira/browse/RFPL-78 > Project: RichFaces Planning > Issue Type: Task > Components: administration, build, site > Affects Versions: Site > Reporter: Jay Balunas > Assignee: Jay Balunas > Priority: Critical > Fix For: 3.3.2.CR1, Site > > Attachments: 8-18-2009-rf-team-meeting-transcript.rtf > > > From Meeting minutes - http://www.jboss.org/community/wiki/RichFacesTeamMeetingMinutes8-18-2009 > Wiki: http://www.jboss.org/community/wiki/RichFaces33xReleaseProcedure > * item 15 needs to be updated > * Don't need to update demos except for GA > * Expand "When QE/Dev ready - release" > o Need steps and details > o Upload to downloads.jboss.org and others ( see attached transcript) > * Magnolia site update requirements > * Listing of all places that need updated ( wikipedia, twitter, blog, etc...) > This will involve Konstantin as well -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 4 months

1
0
0 / 0

[JBoss JIRA] Commented: (RFPL-78) Update 3.3.X release procedure based on comments from team meeting

by Jay Balunas (JIRA)

[ https://jira.jboss.org/jira/browse/RFPL-78?page=com.atlassian.jira.plugin... ] Jay Balunas commented on RFPL-78: --------------------------------- 15 should be: Prep for announcement of release - To be ready for announcement prior to when it is needed. - See step #20 for locations to prep for 20 should be an actual listing of locations - not a couple places and then etc.... - I would like this to be our guide for what sites/places to contact listed out > Update 3.3.X release procedure based on comments from team meeting > ------------------------------------------------------------------ > > Key: RFPL-78 > URL: https://jira.jboss.org/jira/browse/RFPL-78 > Project: RichFaces Planning > Issue Type: Task > Components: administration, build, site > Affects Versions: Site > Reporter: Jay Balunas > Assignee: Jay Balunas > Priority: Critical > Fix For: 3.3.2.CR1, Site > > Attachments: 8-18-2009-rf-team-meeting-transcript.rtf > > > From Meeting minutes - http://www.jboss.org/community/wiki/RichFacesTeamMeetingMinutes8-18-2009 > * item 15 needs to be updated > * Don't need to update demos except for GA > * Expand "When QE/Dev ready - release" > o Need steps and details > o Upload to downloads.jboss.org and others ( see attached transcript) > * Magnolia site update requirements > * Listing of all places that need updated ( wikipedia, twitter, blog, etc...) > This will involve Konstantin as well -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 4 months

1
0
0 / 0

[JBoss JIRA] Assigned: (RFPL-78) Update 3.3.X release procedure based on comments from team meeting

by Konstantin Mishin (JIRA)

[ https://jira.jboss.org/jira/browse/RFPL-78?page=com.atlassian.jira.plugin... ] Konstantin Mishin reassigned RFPL-78: ------------------------------------- Assignee: Jay Balunas (was: Konstantin Mishin) I have done my part. Jay, see Ilya comments, please. > Update 3.3.X release procedure based on comments from team meeting > ------------------------------------------------------------------ > > Key: RFPL-78 > URL: https://jira.jboss.org/jira/browse/RFPL-78 > Project: RichFaces Planning > Issue Type: Task > Components: administration, build, site > Affects Versions: Site > Reporter: Jay Balunas > Assignee: Jay Balunas > Priority: Critical > Fix For: 3.3.2.CR1, Site > > Attachments: 8-18-2009-rf-team-meeting-transcript.rtf > > > From Meeting minutes - http://www.jboss.org/community/wiki/RichFacesTeamMeetingMinutes8-18-2009 > * item 15 needs to be updated > * Don't need to update demos except for GA > * Expand "When QE/Dev ready - release" > o Need steps and details > o Upload to downloads.jboss.org and others ( see attached transcript) > * Magnolia site update requirements > * Listing of all places that need updated ( wikipedia, twitter, blog, etc...) > This will involve Konstantin as well -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 4 months

1
0
0 / 0

[JBoss JIRA] Commented: (RFPL-81) Create a "mailing list" page and section on the new project site

by Jay Balunas (JIRA)

[ https://jira.jboss.org/jira/browse/RFPL-81?page=com.atlassian.jira.plugin... ] Jay Balunas commented on RFPL-81: --------------------------------- richfaces-planning-issues list - https://lists.jboss.org/mailman/listinfo/richfaces-planning-issues richfaces-issues list - https://lists.jboss.org/mailman/listinfo/richfaces-issues richfaces-svn-commits - https://lists.jboss.org/mailman/listinfo/richfaces-svn-commits > Create a "mailing list" page and section on the new project site > ----------------------------------------------------------------- > > Key: RFPL-81 > URL: https://jira.jboss.org/jira/browse/RFPL-81 > Project: RichFaces Planning > Issue Type: Task > Components: site > Affects Versions: Site > Reporter: Jay Balunas > Assignee: Ilya Shaikovsky > Fix For: Site > > > We need a mailing list section that describes our current public mailing list and provides links for joining > richfaces svn > rf jira > rfpl jira > instructions for design/user forum subscription -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 4 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

richfaces-planning-issues August 2009