[
https://jira.jboss.org/jira/browse/RFPL-78?page=com.atlassian.jira.plugin...
]
Jay Balunas reopened RFPL-78:
-----------------------------
Assignee: Konstantin Mishin (was: Jay Balunas)
#14 - we need details of that process. What steps accomplish that goal etc.... Not every
little "cd", but the steps, links and changes to upload. I understand that you
svn commit to the repo, but you must change something so the mvn install updates the svn
version of the repo right - what are those steps.
Also every release should be uploaded to
jboss.org so it can be linked from new site. Not
just for GA/SR releases. This includes project site updates and uploads.
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: Konstantin Mishin
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