Currently merging code to mortic...
Estimated Release Date: ...
Mortic and Sortua follow a closely-tied development cycle. This cycle is almost always followed, except for in odd cases where this cycle doesn't allow for the inclusion of odd features. However, at least bits of this cycle will always be present, and it may be interesting for you to know what our cycle is.
The Development Cycle for Mortic is, with 4 phases, slightly more complicated than that of Sortua. As Sortua is the testbed for new Mortic features, every phase for Sortua is tied directly to another phase for Mortic. These phases are explained below.
- Planning: This is the first phase of development, and is tied to the Planning phase of Sortua. In this phase, new ideas and features are tested and added to Sortua, where all of the inconsistancies are wrinkled out. At the end of this phase, we release version A of Sortua, the version where features are in Sortua's code and not Mortic's.
- Merging: This is where all of the new features in Sortua's code are transferred into Mortic's code. This is also where we come up with ideas for the interface of the new feature, so that it meshes well with the existing interfaces. As before, this phase is tied to the Merging phase of Sortua.
- Testing: After Sortua's development is frozen, we begin to test and refine the features just added to Mortic. At the end of this phase, we should end up with the finished library. All we have left to do is some touch-ups.
- Release: The Release phase of Mortic is when all of the documentation is updated, when the site is updated, and when we finally get a break. This phase should last no longer than a week. In the end, we get a release of both Sortua and Mortic. Hooray!