Development Route Map
The Family Pack is a long term project. The following sets out the current intended order of development and anticipated milestones. In general, the objective of the pre-alpha phase is to achieve a minimum working program that demonstrates the Evidence - Conclusion data model. The alpha phase will concentrate on developing the database design whilst the beta phase will work on the user interface to create an easy and pleasant to use application. The speed of development will depend on many things and so dates are deliberately missing.
The Pre-Alpha versions are not complete, but are being released so the curious can see what the project is about and can, if they wish, provide some feedback.
Add Islamic and Hebrew Calendars to date system.Done.
- Extend the Event system.
These will be the public pre-alpha versions. Again, these will not be complete but will allow people to follow the progress of the project. Some important items that need implementing early.
- Allow connection of multiple databases.
- User created local Calendar system.
- Improve main display to include an expanding tree control.
- Get the Source, Citation and Repositories subsystem working.
- Expand the Name subsystem to separate Persona and Individual names.
- Provide link between Names and Events.
The Alpha phase of this project will concentrate on developing the Database design.
This will be the first public alpha version. This should be the smallest program that demonstrates the Evidence - Interpretation - Conclusion design model. However, I am not able to resist adding a few extras, to see how they work out.
- Develop the Data Confidence methods.
These will be the public alpha versions.
- Develop the Common Data database model.
- Improve the Places subsystem.
- Improve the Historic Events, time line system.
- Complete GEDCOM Export.
- Develop a Name expert system.
The beta phase will develop the user interface to produce a visually attractive and easy to use program.
This will be the first public beta version. I will know when this point arrives as it will be the version that allows me to abandon my current family tree data system and move it onto TFP. This will not be a general recommendation though, since maintenance of the database across versions will be an aim but may not necessarily be achieved.
From this point the versioning system will use a Major, Minor, Revision system where an even Minor number indicates a stable release with only (mostly?) bug fixes applied, whilst odd Minor numbers are used for developing new features and are therefore less stable.
Beta versions developing a working User Interface.
First usable beta. (From this point, Databases will be maintained across upgrades).
Bug fixes to V0.4.0.
Stable Release phase
Once all parts of the database and program are working and fully tested, then Version 1 will be released. Development and bug fixing will continue as before.
First released stable version.