| 1 |
<!DOCTYPE ARTICLE PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> |
<!DOCTYPE ARTICLE PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> |
| 2 |
|
<!-- |
| 3 |
|
$Header$ |
| 4 |
|
$Name$ |
| 5 |
|
--> |
| 6 |
|
|
| 7 |
<article id="MITgcm-Development-HOWTO"> |
<article id="MITgcm-Development-HOWTO"> |
| 8 |
|
|
| 125 |
others. The tree currently resembles:</para> |
others. The tree currently resembles:</para> |
| 126 |
|
|
| 127 |
<programlisting>gcmpack/ |
<programlisting>gcmpack/ |
|
CS-regrid goes into utils |
|
| 128 |
CVSROOT -hidden- |
CVSROOT -hidden- |
| 129 |
|
|
| 130 |
MITgcm code |
MITgcm code |
| 148 |
|
|
| 149 |
acesgrid.org build acesgrid web site |
acesgrid.org build acesgrid web site |
| 150 |
development experimental stuff |
development experimental stuff |
|
gcmpack an old back-up copy ? |
|
| 151 |
gfd_lab -?- |
gfd_lab -?- |
| 152 |
manual -save- |
manual source of MITgcm documentation |
|
misc -?- |
|
| 153 |
mitgcm.org build web site |
mitgcm.org build web site |
| 154 |
mitgcmdoc -> manual -remove- |
old_develop old and early development source |
| 155 |
models -?- |
misc -?- |
| 156 |
packages -?- |
models -?- |
| 157 |
|
packages -?- |
| 158 |
|
preprocess -?- |
| 159 |
pdfs some pdfs |
pdfs some pdfs |
| 160 |
planetinabottle.org unfinished web site |
planetinabottle.org unfinished web site |
|
preprocess -?- |
|
|
tmp -?- |
|
| 161 |
www.ecco-group.org build ecco web site ? |
www.ecco-group.org build ecco web site ? |
| 162 |
</programlisting> |
</programlisting> |
| 163 |
|
|
| 203 |
|
|
| 204 |
<para>As shown in the online <ulink |
<para>As shown in the online <ulink |
| 205 |
url="http://mitgcm.org/viewvc/MITgcm/MITgcm/model/src/forward_step.F?view=graph"> |
url="http://mitgcm.org/viewvc/MITgcm/MITgcm/model/src/forward_step.F?view=graph"> |
| 206 |
ViewCVS-generated tree</ulink>, the MITgcm codebase is split into to two |
ViewCVS-generated tree</ulink>, the MITgcm codebase is split into |
| 207 |
branches or "lines" under which development proceeds. These two lines are |
branches or "lines" under which development proceeds. The main line |
| 208 |
referred to as the "MAIN" and "ecco" versions of the code. While not |
of development is referred to as the "MAIN" version of the code. |
|
identical, the bulk of the MAIN and ecco lines are composed of files from |
|
|
the same codebase. |
|
| 209 |
</para> |
</para> |
| 210 |
|
|
| 211 |
<para>Periodically, a "Release" branch is formed from the "MAIN" |
<para>Periodically, a "Release" branch is formed from the "MAIN" |
| 212 |
development branch. This is done in order to create a relatively stable |
development branch. This is done in order to create a relatively stable |
| 213 |
reference point for both users and developers. The intent is that once a |
reference point for both users and developers. The intent is that once a |
| 214 |
relese branch has been created, only bug-fixes will be added to it. |
release branch has been created, only bug-fixes will be added to it. |
| 215 |
Meanwhile, development (which might "break" or otherwise render invalid |
Meanwhile, development (which might "break" or otherwise render invalid |
| 216 |
the documentation, tutorials, and/or examples contained within a release |
the documentation, tutorials, and/or examples contained within a release |
| 217 |
branch) is allowed to continue along the MAIN and ecco lines.</para> |
branch) is allowed to continue along the MAIN line.</para> |
| 218 |
</sect2> |
</sect2> |
| 219 |
|
|
| 220 |
<sect2> |
<sect2> |
Parent Directory
| 
Revision Log
| 
Revision Graph
| 
Patch