* TODO: Update the list with the postponed todo items.

* configure.in: Increment release number.


svn: r2184
This commit is contained in:
Alex Roitman 2003-09-30 00:08:45 +00:00
parent 78aa304a39
commit 23b26aa5fe
3 changed files with 21 additions and 17 deletions

View File

@ -1,3 +1,7 @@
2003-09-29 Alex Roitman <shura@alex.neuro.umn.edu>
* TODO: Update the list with the postponed todo items.
* configure.in: Increment release number.
2003-09-28 Don Allingham <dallingham@users.sourceforge.net> 2003-09-28 Don Allingham <dallingham@users.sourceforge.net>
* Version 0.9.4: the "This used to bug me..." release. * Version 0.9.4: the "This used to bug me..." release.

View File

@ -1,18 +1,3 @@
* Add support for storing reliability (confidence) of the marriage information;
see http://sourceforge.net/mailarchive/forum.php?thread_id=3066997&forum_id=1993
and http://sourceforge.net/mailarchive/forum.php?thread_id=3134931&forum_id=1993
for the details.
* Work out the model and the interface for the completeness of a person,
see http://sourceforge.net/mailarchive/forum.php?thread_id=3127454&forum_id=1993
and http://sourceforge.net/mailarchive/forum.php?thread_id=3134932&forum_id=1993
for the details.
* Presense of Notes for a person/event/whatever_else. RFE 747527 suggested
either a column in the People View or something like boldfaces "Notes"
tab title. I like the latter because it can be uniformly applied to
any notes, not only people's. Not so hard to implement.
* Allow for multiple notes. A tabbed interface would be really useful, * Allow for multiple notes. A tabbed interface would be really useful,
since there are no titles for notes. Not all objects would necessarily since there are no titles for notes. Not all objects would necessarily
need multiple notes. Determine which ones should and shouldn't. need multiple notes. Determine which ones should and shouldn't.
@ -26,7 +11,22 @@
try to create a thumbnail in a readonly database. try to create a thumbnail in a readonly database.
* Startup tips. * Startup tips.
* Add sequence number to childlist in family view * Add sequence number to childlist in family view
* Add completeness level to person/family
* Add string substitutions for web page generation (name, report name, * Add string substitutions for web page generation (name, report name,
date, etc). date, etc).
* Add support for sources of the parent/child relation
* Add support for storing reliability (confidence) of the marriage information;
see http://sourceforge.net/mailarchive/forum.php?thread_id=3066997&forum_id=1993
and http://sourceforge.net/mailarchive/forum.php?thread_id=3134931&forum_id=1993
for the details.
* Work out the model and the interface for the completeness of a person,
see http://sourceforge.net/mailarchive/forum.php?thread_id=3127454&forum_id=1993
and http://sourceforge.net/mailarchive/forum.php?thread_id=3134932&forum_id=1993
for the details.
* Presense of Notes for a person/event/whatever_else. RFE 747527 suggested
either a column in the People View or something like boldfaces "Notes"
tab title. I like the latter because it can be uniformly applied to
any notes, not only people's. Not so hard to implement.
* Replace ListModel with the TreeModel
* Work out BookReport dialog so that resize is not necessary
* Work out name capitalization options
* And a whole lot more.... * And a whole lot more....

View File

@ -5,7 +5,7 @@ AC_PREREQ(2.57)
AC_INIT(gramps, 0.9.4, gramps-bugs@lists.sourceforge.net) AC_INIT(gramps, 0.9.4, gramps-bugs@lists.sourceforge.net)
AC_CONFIG_SRCDIR(src/gramps.py) AC_CONFIG_SRCDIR(src/gramps.py)
AM_INIT_AUTOMAKE(1.6.3) AM_INIT_AUTOMAKE(1.6.3)
RELEASE=0.CVS$(head -c 10 ${srcdir}/ChangeLog | tr -d '-') RELEASE=1.CVS$(head -c 10 ${srcdir}/ChangeLog | tr -d '-')
VERSIONSTRING=$VERSION VERSIONSTRING=$VERSION
if test x"$RELEASE" != "x" if test x"$RELEASE" != "x"