-
1. Re: Production Release Criteria
ovidiu.feodorov Feb 3, 2006 11:24 AM (in response to ovidiu.feodorov)Ryan wrote:
Yes, we can do this. Take a look at these two wikis. We'd like to create one just for messaging.
All project's checklist:
http://wiki.jboss.org/wiki/Wiki.jsp?page=QAPreReleaseChecklist
Cache project's checklist
http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossCacheQA -
2. Re: Production Release Criteria
ovidiu.feodorov Feb 3, 2006 11:25 AM (in response to ovidiu.feodorov)We already have this: http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossMessagingReleaseChecklist
My question was: If I send a release bundle to QA, what are the criteria QA uses to decide that the bundle is "releasable" or not? -
3. Re: Production Release Criteria
ryan.campbell Feb 3, 2006 5:45 PM (in response to ovidiu.feodorov)At this point I would think:
1. all unit tests pass
2. all integration tests in AS 4.0 and head pass
What do you think? -
4. Re: Production Release Criteria
ovidiu.feodorov Feb 3, 2006 6:06 PM (in response to ovidiu.feodorov)1) is taken care of.
I need to hook the new implementation to the integration tests and give it a spin.
Do we have a way to automate this, the same way we do it for unit tests? -
5. Re: Production Release Criteria
ryan.campbell Feb 9, 2006 5:54 PM (in response to ovidiu.feodorov)Yes, we can automate this. Ideally, we would have a jms-integration-matrix build on cruisecontrol which would daily test jms against your target servers, both those under development (4.0.x, 5.0.x) and eventually, those which have been released.
Basically, this build would deploy jms to each server and patch their configurations, and then run the testsuite (or perhaps just the jms tests?).
http://jira.jboss.com/jira/browse/JBQA-293