9:35 a.m.
User development,
The document "JBossCache2.xQA", was updated Feb 22, 2010
by Manik Surtani.
To view the document, visit:
http://community.jboss.org/docs/DOC-10245#cf
Document:
--------------------------------------------------------------
h2. QA Process for JBoss Cache
http://wiki.jboss.org/wiki/Wiki.jsp?page=QAPreReleaseChecklist
1. 2 weeks prior to release the JBoss Cache team should open a JIRA issue in the JBoss QA
project detailing what will be released, the date it is expected to be released on, and
the CVS tag which will be used for the release. The JIRA will also note the name of any
JBoss AS release (or AS branch head) with which the release must be compatible.
2. On release day Cache team will tag their project appropriately and enter a comment on
the JIRA issue notifying QA that the project is now ready for the QA process. This Jira
issue lives under component
JBossCache
?
3. QA team checks out JBoss Cache from cvs by tag
3.1. +cvs -d:pserver:mailto:anonymous@anoncvs.forge.jboss.com:/cvsroot/jboss co -r TAG
JBossCache
+
5. Check if the version information has been updated in /build.xml and
src/org/jboss/cache/Version.java
6. Cache also requires the module docbook-support
6.1. svn co https://svn.jboss.org/repos/jbossas/trunk/docbook-support docbook-support
8. QA team then builds the cache project using the target distr
8.1. Build should be performed using *JDK 5.0* version compiler
8.2. cd JBossCache
8.3. ./build.sh dist. This will produce the following packages:
8.3.1. JBossCache-core-xxx. Core Cache.
8.3.2. JBossCache-pojo-xxx. A superset of core plus PojoCache
8.3.3. JBossCache-all-xxx. Everything plus Javadocs.
8.3.4. bdbje-for-JBossCache-xxx. This can't be bundled so it's a separate
package.
10. QA team will run the JBossCache testsuite
10.1. Problems were encountered due to the following files /tmp/je.lck, /tmp/00000000.jdb
being present
10.2. Attempt to remove these file before running the testsuite
10.3. Delete all /tmp/JBossCache-, /tmp/Tx, /tmp/a. directories created during the
previous run of the cache testsuite.
10.4. Expect other existing files in /tmp to break tests
10.5. ./build.sh all-unittests-cc -Djava.awt.headless=true
10.6. ./build.sh reports
10.7. Examine the reports using cruisecontrol as a baseline, look for any nuances
10.8. Rerun with one-test[Pojocache|-pojocache] -Dtest=<test_case>
-Djgroups.stack=<udp/tcp>
12. Sanity checking
12.1. QA team will run the distro testsuite (suggesting from -pojo distro)
12.1.1. Under the unzip directory, ./build.sh run.batch and ./build.sh
run.pojocache.batch
12.1.2. That's the same test suite as above but tests are precompiled and no udp/tcp
option
12.1.3. The sleepycat jar is required for passage of all tests (in the
bdbje-for-JBossCache
)
12.3. Check all documentation is present and looks ok
12.4. Examine the Changelog.txt
12.5. Run through the tutorial page under Tutorial doc
12.5.1. Under both Dos and Linux
12.7. Run and validate output for examples under /examples/PojoCache/ , instructions to
run these examples can be found in /examples/PojoCache//readme.txt
12.8. Run the beanshell tests (Following instruction apply to pre cache 2.0 version). For
2.0 version, to run bean shell, simply follow instructions at
dist/JBossCache-all-$VERSION/docs/tutorial/en/html_single/index.html. It's much
easier)
12.8.1. from the root dir execute runShellDemo
12.8.1.1. once the beanshell gui has started there 4 bsh files which can be executed,
pojocacheWithTx, pojocache, oodb, and plain
12.8.1.2. To execute them type: sourceRelative("plain.bsh");
12.8.1.3. See the tutorial under docs/tutorial/en/pdf/TreeCache.pdf & tutorial-pojo
(Section 6: Demo) for further instructions.
12.8.1.3.1. Section 6: Plain Cache, to run plain.bsh
12.8.1.3.2. Section 7: CacheLoader Examples, to run oodb.bsh
12.8.1.3.3. Verify JBCACHE-680
12.8.1.5. See the tutorial under docs/tutorial-pojo/en/pdf/TreeCache.pdf (Section 6: Demo)
for further instructions on PojoCache.
12.8.1.5.1. Section 7: PojoCache, to run pojocache.bsh
12.8.1.5.2. Section 8: PojoCache with Transaction, to run PojoCacheWithTx.bsh
14. QA will confirm proper integration with JBoss AS
14.1. The JIRA issue in the QA project will identify any AS release(s) (or branch(es), if
the release is meant to be integrated into an unreleased AS version) with which the
release must be compatible. If no such release is listed, AS integration testing is not
required.
14.2. Check out and build the indicated AS release.
14.3. Replace the /build/output/jboss-xxx/server/all/lib/jboss-cache.jar with the jar from
the new JBC release.
14.4. Replace the /build/output/jboss-xxx/server/all/lib/pojocache.jar with the jar from
the new JBC release. (Note this is new in 2.0 release.)
14.5. Execute the tests-clustering-all-stacks target in the testsuite
14.6. Check for regressions vs. the JBC release previously included with the release.
16. After passing the tests upload the JBossCache-core-2.x.y.zip,
JBossCache-pojo-2.x.y.zip, JBossCache-core-JDK140-2.x.y.zip, JBossCache-all-2.x.y,
bdbje-for-JBossCache-2.x.y.zip files found in /dist
17. MD5 checksums should be generated as well
17.1. ftp upload.sourceforge.net/incoming
19. Release on sourceforge
19.1. login to sourceforge and go to jboss project
19.2. administer project
19.3. select jboss-cache
19.4. make a new release
19.5. release the project
21. Release the binary to the repository (now contains jboss-cache.jar and pojocache.jar)
21.1. Check both the jboss-cache.jar, pojocache.jar and jboss-cache-jdk50.jar into the
repository
21.1.1. https://svn.jboss.org/repos/repository.jboss.org/jboss/cache
21.3. DO NOT modify the build/build-thirdparty file in any JBoss AS branch. Doing this is
the responsibility of the AS developers.
21.4. Release the binary to the Maven2 repository
21.4.1. https://svn.jboss.org/repos/repository.jboss.org/maven2/jboss/jboss-cache
--------------------------------------------------------------