Difference between revisions of "Tagged Versions"
Jump to navigation
Jump to search
Line 3: | Line 3: | ||
{| class="wikitable" | {| class="wikitable" | ||
|- | |- | ||
! Tag !! Date !! | ! Tag !! Revision !! Date !! NairnMPM Version !! NairnFEA Version !! NairnFEAMPMViz Version | ||
|- | |- | ||
| release-5.0 || xx || 9 FEB 2014 || 8.2.0 || 2.9.0 || 3.3.0 | | release-5.0 || xx || 9 FEB 2014 || 8.2.0 || 2.9.0 || 3.3.0 |
Revision as of 15:28, 9 February 2014
The project nairn-mpm-fea was first imported to googlecode.com in December 2009. The first imported version was tagged as release 1.0. The following table lists tag, dates, and version numbers of subcomponents for all available tagged versions:
Tag | Revision | Date | NairnMPM Version | NairnFEA Version | NairnFEAMPMViz Version |
---|---|---|---|---|---|
release-5.0 | xx | 9 FEB 2014 | 8.2.0 | 2.9.0 | 3.3.0 |
release-4.0 | 592 | 9 JAN 2013 | 9.0.0 | 3.0.0 | 4.0.0 |
release-3.0 | 366 | 25 JAN 2012 | 8.2.0 | 2.9.0 | 3.3.0 |
release-2.0 | 188 | 25 JUL 2010 | 7.3.0 | 2.7.1 | 3.1.0 |
release-1.0 | 65 | 30 DEC 2009 | 7.2.0 | 2.7.0 | 3.0.0 |
You can checkout a tagged version if needed.
Tagging a Version by Committers
When the current main trunk is stable, you can store a tagged version with the command
svn copy https://nairn-mpm-fea.googlecode.com/svn/trunk \ https://nairn-mpm-fea.googlecode.com/svn/tags/release-2.2 \ -m "Tagging stable release 2.2"
where you enter any unused release number. This option should only be use for major releases because revision number suffices to track minor version changes.