3.4 Roadmap - Revision history

Daleathan: /* Gramps 3.4 */

2012-09-01T02:28:18Z

‎Gramps 3.4

Kulath: Provide bugtracker item for GEDCOM import report

2012-02-26T22:53:26Z

Provide bugtracker item for GEDCOM import report

Kulath: /* Main goals */ Updated to add GEPS 023 (because this is now in trunk)

2011-12-28T21:46:37Z

‎Main goals: Updated to add GEPS 023 (because this is now in trunk)

Gioto: /* Minor goals */

2011-10-14T04:00:41Z

‎Minor goals

Gioto: /* Minor goals */

2011-10-14T03:59:49Z

‎Minor goals

Gioto: * Update Python 3 Deprecated list ?

2011-10-14T03:49:12Z

* Update Python 3 Deprecated list ?

Gioto: /* Gramps 3.3 */

2011-10-14T03:48:39Z

‎Gramps 3.3

Daleathan at 04:39, 18 June 2011

2011-06-18T04:39:23Z

Daleathan: /* Dependency upgrades */

2011-06-18T04:38:27Z

‎Dependency upgrades

Daleathan: /* Policy changes */

2011-06-18T04:33:43Z

‎Policy changes

@@ Line 56: / Line 56: @@
 For 3.4:
 * Update [[Python 3 Deprecated]] list ?
-* python 3.x?
+* {{bug|2620}}: Python 3.X support?
 ==Database backend changes==

@@ Line 79: / Line 79: @@
 * (''remain [[3.2_Roadmap#Minor_goals|roadmap 3.2]]'') '''Remove memory leaks present in glade loading code'''. bug tracker: [http://www.gramps-project.org/bugs/view.php?id=2616] - these changes might be backported to 3.2 depending on the code size. ''Developers'': Benny, gburto01.
-* (''remain [[3.2_Roadmap#Minor_goals|roadmap 3.2]]'') '''GEDCOM import error/warnings report'''. bug tracker: todo - provide a report of GEDCOM errors and warnings after import to show the user what information has not been imported. ''Developers'': gburto01.
+* (''remain [[3.2_Roadmap#Minor_goals|roadmap 3.2]]'') '''GEDCOM import error/warnings report'''. bug tracker: [http://www.gramps-project.org/bugs/view.php?id=5599] - provide a report of GEDCOM errors and warnings after import to show the user what information has not been imported. ''Developers'': kulath.
 * (''remain [[3.2_Roadmap#Minor_goals|roadmap 3.2]]'') '''First version of Gramps on-line webapp''': A multi-user, collaboration-focused version of Gramps. Based on Django Python web framework tools. See [[GEPS 013: GRAMPS Webapp]]. ''Developers'': Doug B. and Kathy M.
 * '''Update Graphical reports'''. [http://gramps.svn.sourceforge.net/viewvc/gramps?view=revision&revision=16348] ''Developers'': Graig A.

@@ Line 71: / Line 71: @@
 * '''Refractor Geoview''' ''Developers'': Serge/Benny - ''Reviewers'': ?
 * '''Update API documentation''': bug tracker:[http://www.gramps-project.org/bugs/view.php?id=2691]. ''Developers'': ? - ''Reviewers'': ? - ''Status'': Sphinx with RestructuredText is chosen, see [http://www.gramps-project.org/docs]
 * [http://gramps-project.org/wiki/index.php?title=Category:GEPS GEPS]
 ...

@@ Line 85: / Line 85: @@
 * '''Fix bug''' on [http://www.gramps-project.org/bugs/roadmap_page.php?version_id=18 3.3] roadmap and last remain issues for [http://www.gramps-project.org/bugs/roadmap_page.php?project_id=6 3.2].
 * '''Feature Requests''':
-# [[Display formatting3 3]]: Graig A.
+# [[Display formatting]]: Graig A.
 # [http://www.gramps-project.org/bugs/view.php?id=4400 Lunisolar calendar] support ?

@@ Line 82: / Line 82: @@
 * '''Update Graphical reports'''. [http://gramps.svn.sourceforge.net/viewvc/gramps?view=revision&revision=16348] ''Developers'': Graig A.
 * '''Use new Exporter feature on reports''' or proxies support on reports. bug tracker: [http://www.gramps-project.org/bugs/view.php?id=3878]
-* '''Clean-up''' see [[Deprecated]] (python 3)
+* '''Clean-up''' see [[Python 3 Deprecated]] (python 3)
 * '''Fix bug''' on [http://www.gramps-project.org/bugs/roadmap_page.php?version_id=18 3.3] roadmap and last remain issues for [http://www.gramps-project.org/bugs/roadmap_page.php?project_id=6 3.2].
 * '''Feature Requests''':
 # [[Display formatting3 3]]: Graig A.
 # [http://www.gramps-project.org/bugs/view.php?id=4400 Lunisolar calendar] support ?

@@ Line 51: / Line 51: @@
 For 3.3:
 * Only support Python 2.6 or later (''configure.in, gramps.py, windows/builder/gramps2.nsi'')
-* Update [[Deprecated]] list ?
+* Update [[Python 3 Deprecated]] list ?
 ===Gramps 3.4===

@@ Line 28: / Line 28: @@
 ==Dependency upgrades==
-==Gramps 3.1==
+===Gramps 3.1===
 For 3.1 we have: Python 2.5 or greater, PyGTK2 2.10 or greater, Python Glade bindings, librsvg2 (svg icon view), xdg-utils
 Recommended or optional: GraphViz, gtkspell, ttf-freefont. Documentation is in mediawiki.
-==Gramps 3.2==
+===Gramps 3.2===
 For 3.2:
 * change to PyGTK 2.12. Reason: Move away from libglade to GtkBuilder. Info: [http://www.micahcarrick.com/05-30-2008/gtk-builder-libglade-faq.html], example: [http://www.micahcarrick.com/01-01-2008/gtk-glade-tutorial-part-3.html]. ''Developers'': ? - ''Reviewers'': ?
@@ Line 48: / Line 48: @@
 * it appears there is a drive to use enchant for spell checking. The API is better than gtkspell and has a python interface. We should investigate if we should not move entirely to this package and deprecate gtkspell. At a minimum we will look into adding  enchant as a possible spell checking backend to GRAMPS, using it when installed. Packagers could then choose to let GRAMPS depend on enchant or gtkspell (part of gnome-extras now). ''Developers'': Benny, ''Status'': enchant is working
-==Gramps 3.3==
+===Gramps 3.3===
 For 3.3:
 * Only support Python 2.6 or later (''configure.in, gramps.py, windows/builder/gramps2.nsi'')
 * Update [[Deprecated]] list ?
-==Gramps 3.4==
+===Gramps 3.4===
 For 3.4:
+*

@@ Line 28: / Line 28: @@
 ==Dependency upgrades==
 For 3.1 we have: Python 2.5 or greater, PyGTK2 2.10 or greater, Python Glade bindings, librsvg2 (svg icon view), xdg-utils
 Recommended or optional: GraphViz, gtkspell, ttf-freefont. Documentation is in mediawiki.
 For 3.2:
 * change to PyGTK 2.12. Reason: Move away from libglade to GtkBuilder. Info: [http://www.micahcarrick.com/05-30-2008/gtk-builder-libglade-faq.html], example: [http://www.micahcarrick.com/01-01-2008/gtk-glade-tutorial-part-3.html]. ''Developers'': ? - ''Reviewers'': ?
 * keep python 2.5 compatibility, while preparing for python 3.x.
-Reason: At the moment there are no features of the 2.6/7 version
+Reason: At the moment there are no features of the 2.6/7 version GRAMPS needs that require python 2.5 support to be dropped. Version
-GRAMPS needs that require python 2.5 support to be dropped. Version
+.2 will however be the last GRAMPS version on python 2.x, with the next version of GRAMPS (3.3) being python 3.x only. For that reason,
-.2 will however be the last GRAMPS version on python 2.x, with the
+the move to python 3.0 needs to be prepared. For this we need the support that python 2.6 offers. That is, people should start to run
 next version of GRAMPS (3.3) being python 3.x only. For that reason,
 the move to python 3.0 needs to be prepared. For this we need the
 support that python 2.6 offers. That is, people should start to run
 GRAMPS with:
     python -3 gramps.py
-which will print out depreciation warnings for all syntax that is not
+which will print out depreciation warnings for all syntax that is not compatible with Python 3.0. The goal is then to clean up all Python
-compatible with Python 3.0. The goal is then to clean up all Python
+.0 depreciation warnings using the new functionality that python 2.6 offers for this, while still providing fallback for python2.5 (using
 .0 depreciation warnings using the new functionality that python 2.6
 offers for this, while still providing fallback for python2.5 (using
 eg __future__ module and try, except blocks).
-Should somebody come forward with an important improvement that
+Should somebody come forward with an important improvement that requires python2.6, or if removing the warnings of python -3 is impossible with backward python2.5 compatibility present, keeping python2.5 compatibility can be dropped after talking it through on the devel list. In other words, support for python2.5 should not be dropped without giving it a try first.
 requires python2.6, or if removing the warnings of python -3 is
 impossible with backward python2.5 compatibility present, keeping
 python2.5 compatibility can be dropped after talking it through on the
 devel list. In other words, support for python2.5 should not be
 dropped without giving it a try first.
 ''Developers'': All
 * it appears there is a drive to use enchant for spell checking. The API is better than gtkspell and has a python interface. We should investigate if we should not move entirely to this package and deprecate gtkspell. At a minimum we will look into adding  enchant as a possible spell checking backend to GRAMPS, using it when installed. Packagers could then choose to let GRAMPS depend on enchant or gtkspell (part of gnome-extras now). ''Developers'': Benny, ''Status'': enchant is working
 For 3.3:
 * Only support Python 2.6 or later (''configure.in, gramps.py, windows/builder/gramps2.nsi'')
 * Update [[Deprecated]] list ?
 For 3.4:
-−
+*
+* python 3.x?
 ==Database backend changes==

@@ Line 15: / Line 15: @@
 Changes to the way developers handle the workflow. This will be decided by the core developers in the near future.
-* A required minimum pylint score of 9. This would require all present code to at least obtain this score? ''Developer to write this policy:'' Brian M.
+* A required minimum [[Programming_guidelines#Pylint |pylint]] score of 9.
-** ''Status: done ([[Developer_Policies#Coding_style]])''
 * Every main goal and database change needs at minimum one developer and one reviewer. We need to avoid situations as with 3.0/3.1 where large code changes where left only partially finished. If the developer drops out, the reviewer can or take over and fix things up, or revert the changes. If there are two developers then it suffices both are also reviewers.
 * svn branches for all large changes that requires multiple checking over a period of time during which the code will be broken (eg database changes and large refactoring). It is mainly up to the developers to do this or not, but this should make it clear how main changes can be added to the codebase without disrupting development of other people for a long period (which should be avoided). See commands eg [http://matforge.org/fipy/browser/trunk/documentation/ADMINISTRATA.txt here].  ''Developer to write this policy:'' ?
 * Decision on the definition of the different parts of GRAMPS. What do we allow as plugins, views, gramplets, ... ? How do we offer the user a non-confusing image of what GRAMPS is? This starts in version 3.1 with not distributing some parts of GRAMPS that are present in the subversion repository.  ''Developer to write this policy:'' bmcage. First scribles: [[GEPS 012: Ecosystem_definition]]
-* Decision on a tool for adding API documentation to GRAMPS source code. The aim would be to work out the infrastructure to make this possible, and guidelines to the GRAMPS developers. Note that GRAMPS contains some support already, but as since the last version nobody seems to bother this means the present guidelines are or not known, or the syntax not liked, or ... See [http://www.gramps-project.org/bugs/view.php?id=2691 feature request]. ''Developer to write this policy:'' ?
 * Developers must follow guidelines described in [[Howto: Contribute to GRAMPS]]