2:35 p.m.
Setup Hudson for 3.3.x release builds
-------------------------------------
Key: RFPL-106
URL: https://jira.jboss.org/jira/browse/RFPL-106
Project: RichFaces Planning
Issue Type: Task
Affects Versions: 3.3.2.GA
Reporter: Nick Belaevski
Assignee: Nick Belaevski
Fix For: 3.3.2.GA
--
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
2:53 p.m.
New subject: [JBoss JIRA] Updated: (RFPL-106) Setup Hudson for 3.3.x release builds
[
https://jira.jboss.org/jira/browse/RFPL-106?page=com.atlassian.jira.plugi...
]
Nick Belaevski updated RFPL-106:
--------------------------------
Description:
Here is the link describing release procedure for 3.3.x:
http://www.jboss.org/community/wiki/RichFaces33XReleaseProcedure
Briefly:
1. Release procedure start tasks - announcement, SVN locking etc.
2. SVN tag creation
3. Building-deployment using Maven to a local working SVN copy of checked out JBoss.org
Maven repository (only org.richfaces.* is recommended - event this part is ~12 gb in
size)
4. Grab build and start testing
5. Fix issues, retag, rebuild
6. Commit distribution files to Maven repository - build should not be run again - that is
important
7. Release procedure end tasks
I suggest to setup build for 3.3.2.CR1 tag just for testing and then use it to build
3.3.2.GA
Assignee: Prabhat Jha (was: Nick Belaevski)
Setup Hudson for 3.3.x release builds
-------------------------------------
Key: RFPL-106
URL: https://jira.jboss.org/jira/browse/RFPL-106
Project: RichFaces Planning
Issue Type: Task
Affects Versions: 3.3.2.GA
Reporter: Nick Belaevski
Assignee: Prabhat Jha
Fix For: 3.3.2.GA
Here is the link describing release procedure for 3.3.x:
http://www.jboss.org/community/wiki/RichFaces33XReleaseProcedure
Briefly:
1. Release procedure start tasks - announcement, SVN locking etc.
2. SVN tag creation
3. Building-deployment using Maven to a local working SVN copy of checked out JBoss.org
Maven repository (only org.richfaces.* is recommended - event this part is ~12 gb in
size)
4. Grab build and start testing
5. Fix issues, retag, rebuild
6. Commit distribution files to Maven repository - build should not be run again - that
is important
7. Release procedure end tasks
I suggest to setup build for 3.3.2.CR1 tag just for testing and then use it to build
3.3.2.GA
--
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
3:17 p.m.
New subject: [JBoss JIRA] Commented: (RFPL-106) Setup Hudson for 3.3.x release builds
[
https://jira.jboss.org/jira/browse/RFPL-106?page=com.atlassian.jira.plugi...
]
Prabhat Jha commented on RFPL-106:
----------------------------------
Created
http://hudson.qa.jboss.com/hudson/view/Richfaces-Release/job/richfaces-3....
This still needs to be modified but will do when my questions are answered.
Setup Hudson for 3.3.x release builds
-------------------------------------
Key: RFPL-106
URL: https://jira.jboss.org/jira/browse/RFPL-106
Project: RichFaces Planning
Issue Type: Task
Affects Versions: 3.3.2.GA
Reporter: Nick Belaevski
Assignee: Prabhat Jha
Fix For: 3.3.2.GA
Here is the link describing release procedure for 3.3.x:
http://www.jboss.org/community/wiki/RichFaces33XReleaseProcedure
Briefly:
1. Release procedure start tasks - announcement, SVN locking etc.
2. SVN tag creation
3. Building-deployment using Maven to a local working SVN copy of checked out JBoss.org
Maven repository (only org.richfaces.* is recommended - event this part is ~12 gb in
size)
4. Grab build and start testing
5. Fix issues, retag, rebuild
6. Commit distribution files to Maven repository - build should not be run again - that
is important
7. Release procedure end tasks
I suggest to setup build for 3.3.2.CR1 tag just for testing and then use it to build
3.3.2.GA
--
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
4:29 p.m.
New subject: [JBoss JIRA] Resolved: (RFPL-106) Setup Hudson for 3.3.x release builds
[
https://jira.jboss.org/jira/browse/RFPL-106?page=com.atlassian.jira.plugi...
]
Nick Belaevski resolved RFPL-106.
---------------------------------
Resolution: Rejected
Current release procedure cannot be executed on Hudson. We'll continue using the
current environment.
Setup Hudson for 3.3.x release builds
-------------------------------------
Key: RFPL-106
URL: https://jira.jboss.org/jira/browse/RFPL-106
Project: RichFaces Planning
Issue Type: Task
Affects Versions: 3.3.2.GA
Reporter: Nick Belaevski
Assignee: Prabhat Jha
Fix For: 3.3.2.GA
Here is the link describing release procedure for 3.3.x:
http://www.jboss.org/community/wiki/RichFaces33XReleaseProcedure
Briefly:
1. Release procedure start tasks - announcement, SVN locking etc.
2. SVN tag creation
3. Building-deployment using Maven to a local working SVN copy of checked out JBoss.org
Maven repository (only org.richfaces.* is recommended - event this part is ~12 gb in
size)
4. Grab build and start testing
5. Fix issues, retag, rebuild
6. Commit distribution files to Maven repository - build should not be run again - that
is important
7. Release procedure end tasks
I suggest to setup build for 3.3.2.CR1 tag just for testing and then use it to build
3.3.2.GA
--
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
6061
days inactive
6075
days old
richfaces-planning-issues@lists.jboss.org
3 comments
2 participants
participants (2)
-
Nick Belaevski (JIRA) -
Prabhat Jha (JIRA)