[Design of JBoss Build System] - New Release Process
by pgier
Here is an outline of what we are thinking as far as a release process for jboss projects:
1) Project lead notifies all developers that no more commits should happen until the release is over.
2) Project lead runs mvn release:prepare -DdryRun=true. This verifies that all the build settings required for a release are available. The release version, and the new trunk version should be communicated to release engineering.
3) Release engineering team runs mvn release:prepare. This creates the tag in svn, and defines the version to be released.
4) Release engineering team runs mvn release:perform. This generates all artifacts from the new tag and deploys them to a staging server.
5) QA uses the artifacts on the staging server to verify that everything works correctly
1. If QA does not find any issues, go to step 6.
2.If QA does find issues with the build, the project goes back to development. Once the issues are resolved, the tag is deleted and the process goes back to step 2.
6)Release engineering promotes the files to production servers.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4032117#4032117
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4032117
18 years, 11 months
[Design the new POJO MicroContainer] - Re: Lifecycle aspects revisited
by kabir.khan@jboss.com
"adrian(a)jboss.org" wrote : The default implementation is to callback on the ControllerContext,
|
| i.e. the last step is necessarily going to happen if the context implementation
| does not extend AbstractControllerContext.
|
You mean if a ControllerContext impl does NOT extend AbstractControllerContext then we miss out on the callbacks.
"adrian(a)jboss.org" wrote :
| I'm arguing that the lifecycle callbacks should apply to at least all
| AbstractControllerContext implementations, not just POJO.
|
I agree and understand that
"adrian(a)jboss.org" wrote :
| Ales thinks that ControllerContextAction should be part of the API so it would
| apply everywhere?
Whereever it goes I think it will be a trivial change, so I will wait for you two to figure out whether it is part of the AOP or not. In any case the "lifecycle information holder" (currently LifecycleBeanMetaData) will need renaming/moving into something visble from the dependency project.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4032081#4032081
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4032081
18 years, 11 months