Difference between revisions of "5.2 Roadmap"

From Gramps
Jump to: navigation, search
(Schedule)
m (Minor goals: * Lossless GEDCOM Export - Custom GEDCOM tags required to round trip import/export via Gramps to GEDCOM to Gramps!)
(8 intermediate revisions by 5 users not shown)
Line 6: Line 6:
 
{| class="wikitable"
 
{| class="wikitable"
 
|-
 
|-
| T.B.A || Agree final roadmap (this document).
+
| T.B.A. || Agree final roadmap (this document).
 
|-
 
|-
| T.B.A || All major features should be merged into master.
+
| T.B.A. || All major features should be merged into master.
 
|-
 
|-
| T.B.A || Feature freeze.
+
| T.B.A. || Feature freeze.
 
|-
 
|-
| T.B.A || String freeze.
+
| T.B.A. || String freeze.
 
|-
 
|-
| 21 April 2021 || Final release.*
+
| T.B.A. || Final release.* whoosh!!
 
|-
 
|-
 
|}
 
|}
 
<nowiki>*</nowiki> Scheduled for the 20th anniversary of Gramps first release April 21, 2001
 
  
 
==Policy changes==
 
==Policy changes==
Line 79: Line 77:
 
* {{bug|10777}} Fulltext search on all elements, objects, items, types which can have a text / string in.
 
* {{bug|10777}} Fulltext search on all elements, objects, items, types which can have a text / string in.
 
* Support Gedcom _UUID.  Two choices 1) extend data model with a list of additional IDs, which would be _UUID or possibly GOVID, GEONamesID etc. 2) Store them in attributes.  The former has advantage that they are invisible to users except for tools explicitly using them, also could easily support db lookup like GrampsID.  The latter limits work to import/export. Gedcom L group has just completed a vote on how they should work for import/export.  Ultimate goal, better merging.
 
* Support Gedcom _UUID.  Two choices 1) extend data model with a list of additional IDs, which would be _UUID or possibly GOVID, GEONamesID etc. 2) Store them in attributes.  The former has advantage that they are invisible to users except for tools explicitly using them, also could easily support db lookup like GrampsID.  The latter limits work to import/export. Gedcom L group has just completed a vote on how they should work for import/export.  Ultimate goal, better merging.
 +
* [[Lossless GEDCOM Export]] - Custom GEDCOM tags required to round trip import/export via Gramps to GEDCOM to Gramps!
  
 
==Rejected Changes==
 
==Rejected Changes==
  
 
+
==Previous Roadmaps==
 +
*[[:Category:Developers/Roadmap|Roadmaps Category]]
  
 
[[Category:Developers/General]]
 
[[Category:Developers/General]]
 
[[Category:Developers/Roadmap]]
 
[[Category:Developers/Roadmap]]

Revision as of 05:40, 15 October 2022

Gramps-notes.png
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

Schedule

T.B.A. Agree final roadmap (this document).
T.B.A. All major features should be merged into master.
T.B.A. Feature freeze.
T.B.A. String freeze.
T.B.A. Final release.* whoosh!!

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.

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.

Suggestions:

Rejected Changes

Previous Roadmaps