202 |
|
|
203 |
<para>As shown in the online <ulink |
<para>As shown in the online <ulink |
204 |
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"> |
205 |
ViewCVS-generated tree</ulink>, the MITgcm codebase is split into to two |
ViewCVS-generated tree</ulink>, the MITgcm codebase is split into |
206 |
branches or "lines" under which development proceeds. These two lines are |
branches or "lines" under which development proceeds. The main line |
207 |
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. |
|
208 |
</para> |
</para> |
209 |
|
|
210 |
<para>Periodically, a "Release" branch is formed from the "MAIN" |
<para>Periodically, a "Release" branch is formed from the "MAIN" |
211 |
development branch. This is done in order to create a relatively stable |
development branch. This is done in order to create a relatively stable |
212 |
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 |
213 |
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. |
214 |
Meanwhile, development (which might "break" or otherwise render invalid |
Meanwhile, development (which might "break" or otherwise render invalid |
215 |
the documentation, tutorials, and/or examples contained within a release |
the documentation, tutorials, and/or examples contained within a release |
216 |
branch) is allowed to continue along the MAIN and ecco lines.</para> |
branch) is allowed to continue along the MAIN line.</para> |
217 |
</sect2> |
</sect2> |
218 |
|
|
219 |
<sect2> |
<sect2> |