Ignore:
Timestamp:
Nov 15, 2006, 7:19:13 PM (17 years ago)
Author:
Jari Häkkinen
Message:

Update to publishing a new release.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/doc/development/index.html

    r2851 r2924  
    426426    <li>
    427427      <p> Make sure that everything that all commits are performed
    428       into to the feature branch. Such as bumping version number in
    429       build.xml. Check that the Application.MAINTENANCE_VERSION constant
    430       is correct. If not change it and commit.</p>
     428      into to the feature branch. Such as bumping version number(s) in
     429      build.xml. The version and build numbers are pushed into
     430      Application.java during packaging or build phase.</p>
    431431    </li>
    432432
     
    434434      <p> Create a tag using a one liner like
    435435<pre>
    436   svn copy http://lev.thep.lu.se/repository/base/branches/2.0.1 \
     436  svn copy http://lev.thep.lu.se/repository/base/branches/2.0.2 \
    437437           http://lev.thep.lu.se/repository/base/tags/2.0.2 \
    438438           -m "Tagging version 2.0.2"
     
    449449<pre>
    450450  svn copy http://lev.thep.lu.se/repository/base/tags/2.0.2 \
    451            http://lev.thep.lu.se/repository/base/branches/2.0.2 \
    452            -m "New bug fix branch for 2.0.2"
     451           http://lev.thep.lu.se/repository/base/branches/2.0.3 \
     452           -m "New bug fix branch for 2.0"
    453453</pre>
    454454      </p>
     
    461461
    462462    <li>
    463       <p> Publish the new version on
     463      <p> Create new binary and source packages with 'ant
     464      package'. Publish the new version on
    464465      <a href=http://base.thep.lu.se/wiki/DownloadPage>the
    465466      wiki</a>. Also make the appropriate update to the download
     
    480481          at revision N and ended at revision M.
    481482<pre>
    482   svn merge -r N:M http://lev.thep.lu.se/repository/base/branches/2.0.1
     483  svn merge -r N:M http://lev.thep.lu.se/repository/base/branches/2.0.2
    483484</pre>
    484485          </p>
     
    495496          <p> Commit changes to trunk.
    496497<pre>
    497   svn commit -m "Merged log:branches/2.0.1#N:M trunk."
     498  svn commit -m "Merged log:branches/2.0.2#N:M trunk."
    498499</pre>
    499500          </p>
     
    506507      <p> Delete the old feature branch using a one liner like
    507508<pre>
    508   svn delete http://lev.thep.lu.se/repository/base/branches/2.0.1 \
    509           -m "Removed obsolete branch 2.0.1 superseded by source:/branches/2.0.2"
     509  svn delete http://lev.thep.lu.se/repository/base/branches/2.0.2 \
     510          -m "Removed obsolete branch 2.0.2 superseded by source:/branches/2.0.3"
    510511</pre>
    511512      </p>
     
    531532    <li>
    532533      <p> Make sure that everything that all commits are performed
    533       into to the feature branch. Such as bumping version number in
    534       build.xml. Check that the Application.MAJOR_VERSION,
    535       Application.MINOR_VERSION and Application.MAINTENANCE_VERSION constant s
    536       are correct. If not change them and commit.</p>
     534      into to the feature branch. Such as bumping version number(s) in
     535      build.xml. The version and build numbers are pushed into
     536      Application.java during packaging or build phase.</p>
    537537    </li>
    538538
     
    555555<pre>
    556556  svn copy http://lev.thep.lu.se/repository/base/tags/2.1 \
    557            http://lev.thep.lu.se/repository/base/branches/2.1 \
     557           http://lev.thep.lu.se/repository/base/branches/2.1.1 \
    558558           -m "New bug fix branch for 2.1"
    559559</pre>
     
    567567
    568568    <li>
    569       <p> Publish the new version on
     569      <p> Create new binary and source packages with 'ant
     570      package'. Publish the new version on
    570571      <a href=http://base.thep.lu.se/wiki/DownloadPage>the
    571572      wiki</a>. Also make the appropriate update to the download
Note: See TracChangeset for help on using the changeset viewer.