For example, we have started a list of maintenance issues for the spec at http://wiki.apache.org/jdo/ChangeLog. And we will start a similar list of maintenance issues for the tck.
Regards, Craig On May 2, 2006, at 8:19 AM, Craig L Russell wrote:
Hi Andy, On May 1, 2006, at 10:50 PM, Andy Jefferson wrote:Hi Craig,Do you have any particular requirements for the release of JPOX 1.1 as RI that weneed to be aware of when releasing ?It has to pass the TCK (now in voting).With respect to CVS tags of the code, I propose tagging the release as JDO_2_RIas well as RELEASE_1_1_0 (our usual release tag)I don't see a problem with this.We will be releasing the usual bundles for 1.1.0 :- 1. Binaries : jpox-1.1.0.jar, jpox-enhancer-1.1.0.jar, jpox-1.1.0.rar 2. Source : jpox-1.1.0-src.tar.gz, jpoz-1.1.0-src.zip, jpox-enhancer-1.1.0-src.tar.gz, jpox-enhancer-1.1.0-src.zip 3. Docs : jpox-docs-1.1.0.tar.gz, jpox-docs-1.1.0.zipIn addition there are (already) 1.1.0 versions of all Plugins (DBCP, C3P0, etc)that are usable with the RI. Anything else ?We assume that the jar files are available for maven to download, so they need to be accessible to tck via tck20/ project.properties:maven.repo.remote = http://www.ibiblio.org/ maven, http://www.jpox.org/downloads/mavenThat's all I can think of. Congratulations. Craig-- AndyCraig Russell Architect, Sun Java Enterprise System http://java.sun.com/products/jdo 408 276-5638 mailto:[EMAIL PROTECTED] P.S. A good JDO? O, Gasp!
Craig Russell Architect, Sun Java Enterprise System http://java.sun.com/products/jdo 408 276-5638 mailto:[EMAIL PROTECTED] P.S. A good JDO? O, Gasp!
smime.p7s
Description: S/MIME cryptographic signature
