Changes between Version 6 and Version 7 of Obsolete/Development/Templates/RelTagging


Ignore:
Timestamp:
Sep 13, 2006, 7:28:16 PM (18 years ago)
Author:
/C=FR/O=CNRS/OU=UMR8607/CN=Michel Jouvin/emailAddress=jouvin@…
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • Obsolete/Development/Templates/RelTagging

    v6 v7  
    5555
    5656As with branch commit, the message must be explicit about the main changes introduced and use the format proposed for branch commit.
    57  
     57
     58Before tagging a new release, be sure to check that examples provided compile successfully. To check this, follow the following steps
     59 * Create a vanilla SCDB
     60 * Load templates to be checked into the vanilla SCDB (with Subversion client or using the tarball)
     61 * Compile with `ant`, the standard tool for compiling with SCDB
     62
     63To do these checks, you don't need to run a Subversion server. You just need a Subversion client and Java for running `ant`.
     64
     65Below is a check example for gLite 3.0.0 branch (replace with the appropriate one) :
     66
     67{{{
     68mkdir /tmp/template-validation
     69cd /tmp/template-validation
     70svn export https://svn.lal.in2p3.fr/SCDB/trunk .
     71cd cfg
     72# In the next command, change the branch to the appropriate one
     73svn export https://svn.lal.in2p3.fr/templates/branches/gLite-3.0.0 .
     74cd ..
     75external/ant/bin/ant
     76}}}
     77
     78Tool [source:templates/trunk/tools/compile-check.sh compile-check.sh] is executing this set of commands and can be used instead of entering command manually.