Mission Statement."To redevelop and update AMOS Professional whilst preserving and maintaining the classic feel and environment of the original."Development Milestones.| Stage1: | Ground Work:
AMOS Pro V2.0 as released and fully documented. This is the "Datum" from which development can proceed. The documentation is well on its way and is databased, so bugs and weird behavior can be pulled out with simple queries.
|
| Stage2: | Code Review:
To facilitate a common development environment whereby everyone is working from common knowledge, the entire source code should be reviewed, cleaned up, documented, modularized, and updated (Known bugs fixed).
AMOS Pro V2.1 with bugs fixed and updated docs. Nothing changed by way of additional functionality. This is the stable base to build the next stage upon.
|
| Stage3: | Primary Enhancements:
AMOS Pro V3.0 with AGA support and fully documented.
|
| Stage4: | Secondary Enhancements:
AMOS Pro V3.0 with approved§ extensions and updated docs. Nothing changed by way of additional functionality. For the extensions, reverse-engineer and pick out the best language-relevant§§ bits from the vast array of existing ones (and bring them into V3.x format). This may well result in just one 'language' extension that is cherry-picked from the 'best of the rest'. With the source now available, this could also be integrated back into the original AMOSPro.Lib if space restrictions aren't broken in the process. For Extensions that are specialised, start an 'approved extensions' register. This would be added to as each one is checked, versioned, fixed if necessary, documented and put into the public domain with some kind of 'approved' sticker.
|
| Stage5: | Development Frozen:
Stop enhancements development except for bug fixes. All further development handed over to Extensions.
|
| Stage6: | A New Beginning:
The project is forked and development on AMOS v3.0 begins. If deemed appropriate any AMOS Pro 3.0 feature can be down-streamed to ClassicAMOS, either as an extension or directly integrated.
|
| | |
| | § - Meaning 'adds worthwhile improvements' and with any bugs fixed. |
| | §§ - Meaning 'adds to the core AMOS functionality' and with any bugs fixed, e.g. AMOSPro_TOME.Lib is not core, AMOSPro_Compiler.Lib is. |
Staged releases will incorporate intermediate version releases (e.g. V2.1.1, V2.1.2, etc.). The process will be a well-defined route from what was released (AMOS Pro V2.0) and where we'd like it to go (presumably AMOS Pro using AGA capabilities and with extra worthwhile extensions as part of the 'approved' package).
This will mean working to a defined set of project/milestone plans.
All the above is aimed squarely at the classic Amiga environment - either real or emulated. If it's any use to AMOS developments in other environments, that's all good. But this particular project is Amiga-only.
Author
Topic: ClassicAMOS Mission Statement / Milestones (Read 5188 times)