Dashboard > iBATIS DataMapper > Home > iBATIS Release Process > Information > Page Comparison
iBATIS Release Process
compared with
Current by Brandon Goodin
on Sep 18, 2008 10:50.

(show comment)
 
Key
These lines were removed. This word was removed.
These lines were added. This word was added.

View page history


There are 1 changes. View first change.

 {panel:title=Quick Links|borderStyle=solid|borderColor=#ccc|titleBGColor=#FAFAF3|bgColor=#FAFAF3}
 # *[First Things First|#first|Things to do first.]*
 # *[iBATIS Release Process|#releaseprocess|The details.]*
 #* *[Beta Release|#beta|The details behind providing a BETA.]*
 #* *[General Availability (GA)|#ga|The details behind releasing a GA.]*
 # *[Java Checklist|#javachecklist|A checklist to help you verify the distribution contents.]*
 #* *[Deploying to iBiblio|#deployingtoibiblio|Step-by-step guide for releasing iBATIS to iBiblio maven repository]*
 # *[.NET Checklist|#cschecklist|A checklist to help you verify the distribution contents.]*
 # *[Resources|#resources|Links to ASF resources.]*
 {panel}
  
 {anchor:first}
 h1. First Things First
 # Read the following pages:
 ## http://wiki.apache.org/incubator/ReleaseManager
 ## http://www.apache.org/dev/mirrors.html
 ## http://apache.org/dev/mirror-step-by-step.html
 # Get your own PGP or GPG key (see http://wiki.apache.org/incubator/SigningReleases).
 # Update the iBATIS KEYS file found in /www/www.apache.org/dist/ibatis/ with your key.
  
 {anchor:releaseprocess}
 h1. iBATIS Release Process
  
 {anchor:beta}
 h2. BETA Quality Release
 # Announce an intent to release (a release plan) on dev@.
 # By convention, try to give the community at least 24 hours to review the plan (lazy consensus).
 # *Update doc/release.txt and build/version.properties*
 # *TAG the SVN Repository* at the trunk level with the release number -- See current tags for examples http://svn.apache.org/repos/asf/ibatis/tags/
 # If needed, update the directory structure in /www/www.apache.org/dist/ibatis/
 # Sign the distribution to create a detached signature file (.asc)
 # Place the BETA distribution, signature file, and MD5 sum in:
 ** /www/www.apache.org/dist/ibatis/
 ** Yes, this is the same directory as GA. In our history we have never rolled back a release, nor do we aggressively release betas unless we intend to release them to GA. Any pre-beta/alpha is expected to be grabbed from SVN directly. Thus, we put betas directly in the GA repository (allowed as per http://apache.org/dev/release.html).
 # Make sure the KEYS file is up to date.
 # Check the upload with the signature and MD5 sum.
 # Change iBATIS web site download links to point to new BETA
 # *Wait at least 24 hours for mirrors to obtain latest release file(s).*
 # Check mirrors for files.
 # If needed, contact Vadim about statistics.
 # Announce BETA on user lists.
  
 {anchor:ga}
 h2. GENERAL AVAILABILITY (GA) Quality Release
 # If a BETA release is pending, give the community a reasonable amount of time to try the release. If feedback positive, call for a VOTE to promote the distribution from BETA to a GA (General Availability) release.
 # To reach GA status, a release must have a total of three +1 votes by iBATIS PMC members and more positive votes than negative votes. If the votes are not forthcoming, scratch this release plan and start over with a new plan and a new version number.
 # Relink "current release" links on the website
 # Announce promotion of the build to GA on user lists.
 # Note: Just because we say that a release is of GA grade today, does not mean we can't change our minds. If a security issue arose, we could downgrade the quality to BETA.
  
 {anchor:javachecklist}
 h1. Java-specific Checklist
  
 h2. Steps
  
 # Update release.txt with changes (usually can be copied straight from JIRA roadmap
 # Update version.properties and build.properties with appropriate MAJOR version numbers (don't modify build number by hand)
 # Run build.bat, ensure SUCCESSFUL build
 # Check the exploded directory for proper directory structure
 # Check the deploy directory for the ZIP file, with proper filename version
  
 {anchor:deployingtoibiblio}
 h2. Deploying to iBiblio the Apache way
  
 # Create a local directory to mirror the people.apache.org maven rsync repo. I just do: mkdir -p ~/apache-m2-repo/org/apache/ibatis
 # cd to the org/apache/ibatis directory and run:
 {code:title=SCP down current repo state|borderStyle=solid}
 scp -r <username>@people.apache.org:/www/people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/ibatis/* ./
 {code}\\This will retrieve a copy of existing releases in the apache maven repo so that when you run your local deploy it will properly setup the maven-metadata.xml files.
 # Get the ant build zip distribution from whoever built it and unzip it to a local directory
 # cd to the src directory in the ibatis distribution where the ibatis-sources.zip file is located and run the following:
 {note:title=Please note}
 * Be sure to replace the <...> content with correct information.
 * The local-directory is the absolute path to the top level directory you setup in step 1 (ex. /Users/brandongoodin/apache-m2-repo)
 {note}
 {warning:title=Warning}
 * You MUST deploy src first because if you try to deploy it after it will overwrite the ibatis-sqlmap<version>.pom with a java-source packaging. Setting the -DgeneratePom=false will cause a nullpointer exception (yeah maven! :/).
 {warning}
 {code:title=Source Deploy|borderStyle=solid}
 mvn deploy:deploy-file -Durl=file:<local-directory> \
  -Dfile=ibatis-src.zip \
  -DgroupId=org.apache.ibatis \
  -DartifactId=ibatis-sqlmap \
  -Dversion=2.3.4.726 \
  -Dpackaging=java-source
 {code}
 # cd to the lib directory in the unzipped distribution and run the following.
 {note:title=Please note}
 * Be sure to replace the <...> content with correct information.
 * The local-directory is the absolute path to the top level directory you setup in step 1 (ex. /Users/brandongoodin/apache-m2-repo)
 * Be sure to include the full version number (ex. 2.3.4.726)
 {note}
 {code:title=Binary Deploy|borderStyle=solid}
 mvn deploy:deploy-file -Durl=file:<local-directory> \
  -Dfile=ibatis-<version>.jar \
  -DgroupId=org.apache.ibatis \
  -DartifactId=ibatis-sqlmap \
  -Dversion=<version> \
  -Dpackaging=jar
  
 {code}
 # cd to the ~/apache-m2-repo/org/apache/ibatis/ibatis-sqlmap/<version> and sign the artifacts (jars and pom) by running
  {code:title=Signing the JAR|borderStyle=solid}
  {code:title=Signing the JAR and POM|borderStyle=solid}
 for i in *.jar; do gpg --output $i.asc --detach-sig --armor $i; done
 for i in *.pom; do gpg --output $i.asc --detach-sig --armor $i; done
 {code}
 # cd to ~/apache-m2-repo/org/apache/ibatis/ibatis-sqlmap/
 # scp new maven-metadata files and new deployed version to people.apache.org by running the following.
 {code:title=SCP new maven-metadata and artifacts|borderStyle=solid}
 scp maven-metadata.x* <username>@people.apache.org:/www/people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/ibatis/ibatis-sqlmap/
 scp -r <version> <username>@people.apache.org:/www/people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/ibatis/ibatis-sqlmap/
 {code}
  
 {anchor:cschecklist}
 h1. .NET-specific Checklist
  
 h2. Assembly/Binary Distribution
 * ASF "LICENSE" text file (see http://apache.org/dev/apply-license.html and http://wiki.apache.org/general/LicenseFormats)
 * Castle.DynamicProxy assembly
 * Castle.DynamicProxy license text file
 * log4net assembly
 * log4net license text file
 * Sample sqlMap.config for DataMapper distribution
 * Sample dao.config for DataAccess distribution
 * providers.config file
 ** Check that only sqlServer1.1, OleDb1.1, and Odbc1.1 providers are enabled in the providers.config file
  
 h2. Documentation Distribution
 * ASF "LICENSE" text file (see http://apache.org/dev/apply-license.html and http://wiki.apache.org/general/LicenseFormats)
 * Correct ASF copyright and dates
 * Correct distribution version #
 * CHM format
 * PDF format
 * HTML format
 * SDK CHM format
 ** Check that SDK CHM has:
 *** Correct ASF copyright and dates
 *** Correct distribution version #
 *** Correct title (ex: iBATIS.NET DataMapper 1.2.1)
 *** Correct HTML Help name (ex: DataMapper-1.2.1)
 *** Dev list email address for feedback
  
 h2. NPetshop Distribution
 {note:title=TODO!!!}
 {note}
 * ASF "LICENSE" text file (see http://apache.org/dev/apply-license.html and http://wiki.apache.org/general/LicenseFormats)
 * Proper ASF copyright on source files
 * README or BUILD file explaining build process
  
 h2. Source Distribution
 * ASF "LICENSE" text file (see http://apache.org/dev/apply-license.html and http://wiki.apache.org/general/LicenseFormats)
 * Proper ASF copyright on source files
 * README or BUILD file explaining build process
 * External-Bin/NET/1.1 directory
 ** Check that External-Bin/NET/1.1 includes:
 *** Castle.DynamicProxy assembly
 *** Castle.DynamicProxy license text file
 *** log4net assembly
 *** log4net license text file
 *** README explaining other assembly dependencies
  
 {anchor:resources}
 h1. Resources
  
 h3. ASF Release Process
 * Release Manager FAQ: http://wiki.apache.org/incubator/ReleaseManager
  
 h3. Mirroring
 * Mirroring Step-By-Step (with OpenPGP, md5, creating directories, and linking): http://apache.org/dev/mirror-step-by-step.html
 * Apache Mirroring Resources (Overview): http://www.apache.org/dev/mirrors.html
 * Ant/Jakarta/XML Mirroring HOWTO (with stats): http://people.apache.org/~bodewig/mirror.html
 * Forrest-based interactive mirror download page: http://forrest.apache.org/howto/howto-asf-mirror.html
  
 h3. Signing Releases and MD5 Sums
 * Signing FAQ: http://people.apache.org/~henkp/sig/pgp-key-signing.txt
 * MD5 FAQ: http://people.apache.org/~henkp/md5/doc.html
 * Signing releases: http://wiki.apache.org/incubator/SigningReleases
 * Check signatures: http://people.apache.org/~henkp/sig/
 * Check distribution signatures and MD5 sums: http://people.apache.org/~henkp/cgi-bin/md5.cgi
 * Check downloaded MD5 sums: http://people.apache.org/~henkp/cgi-bin/md5.cgi
  
 h3. Statistics
 * Statistics: http://people.apache.org/~vgritsenko/faq.html
  
 h3. Other
 * Upcoming ASF Certificate Authority: http://ca.apache.org/
  
Site running on a free Atlassian Confluence Open Source Project License granted to OSS. Evaluate Confluence today.
Powered by Atlassian Confluence, the Enterprise Wiki. (Version: 2.5.5 Build:#811 Jul 25, 2007) - Bug/feature request - Contact Administrators