|
This is a guide only. Because of the nature of a volunteer-driven project, it isn't possible to say with any certainty what will happen in the next release. |
This page collects possibilities for the 5.2 version of Gramps
Contents
Schedule
| 1 Jul 2023 | Agree final roadmap (this document). |
| 1 Jul 2023 | All major features should be merged into master. |
| 10 Jul 2023 | Feature freeze. |
| 17 Jul 2023 | String freeze. |
| 31 Jul 2023 | Beta release. |
Policy changes
Project governance
At present, we use a benevolent dictator model. The BD defines the project's strategic direction and has the final say in decisions.
Minimum requirements
Previously we supported all Python and Gtk versions that were commonly found on operating systems most likely to be used by our users. In practice this meant supporting the versions used by the oldest supported Ubuntu LTS release.
The new policy is to support all Python and Gtk versions that have not reached end-of-life on the Gramps release date.
For details see the discussion in the Gramps 5.2 Minimum Python Requirement thread on the mailing list.
Dependency upgrades
Database model changes
Are there features that require database change? This should happen in the beginning of the development cycle. List your requirements here.
- Enhancements to the place structure to support GEDCOM-L PLAC tag
- Allow multiple place Types with date for each
- Deal with 200+ place types
- Allow multiple postal codes and other attribute like data, with date for each
- Allow places to have attributes (for above)
Decision:
Changes to implement the requirements above:
- PlaceName
- Add a list of PlaceAbbrev objects. A PlaceAbbrev object should consist of a some text and associated type (PlaceAbbrevType).
- Add a citation list.
- PlaceRef
- Add a hierarchy type.
- Add a citation list.
- Place
- Replace the place type field with a list of LocationType objects. A LocationType object should consist of a date, PlaceType, and citation list.
- Add an attribute list.
- Add an event reference list.
- PlaceType
- No change. Type mapping should be done in the import/export code.
Major goals
This section lists main goals developers want to achieve. Major goals should be started in a GEPS branch. Major goals require a developer and a reviewer.
Minor goals
This section lists minor goals developers want to achieve. Minor goals can be done by one developer alone.
- A way to attach objects to the database itself Something like the "Researcher"/"Database owner" but including other data. See 6365 & 8734
- 11404 Change location of resource-path file to allow Python pip Wheels. eg: Running a post-install script is not possible with wheels, so it looks like we need another approach. I suggest that we look for the resources in the standard places at run-time. - Nick Hall & Re: (Gramps-devel) tar files, zip files, distutils, etc.