There are a couple of holding factors.
(1) I realised that ImportGrdb was not working, because it had neither been updated for the new database format, nor changed according to [1] to notify the user that he needed to use an old version to import his file. As proposed in [2] I have now committed the change to report an error if the user attempts to use that import.
(2) 0005466: [XML]: need to check empty personref
I accordance with message [3] in response to question [4] on 5488, this fix is now (I believe) finalised and about to be committed (to 3.4.0), so I will wait for that. This will fix a large number of bugs in the bugtracker, as well as avoid problems for users in the future.
My apologies about the changes to strings, but I think these two changes are important enough to need applying, even if the strings are not translated for the time being.
(Of the other changes in [4], 5595 has now been committed, and 2092 has been postponed in accordance with [5]).
I hope this is OK, but I think it is worth getting these two bugs fixed.
[1]
http://gramps.1791082.n4.nabble.com/Status-of-GEPS-023-tp4329141p4329746.html[2]
http://gramps.1791082.n4.nabble.com/Status-of-GEPS-023-tp4329141p4547097.html[3]
http://www.gramps-project.org/bugs/view.php?id=5466#c23698[4]
http://gramps.1791082.n4.nabble.com/prepare-gramps-3-4-tp4329757p4540048.html[5]
http://gramps.1791082.n4.nabble.com/prepare-gramps-3-4-tp4329757p4543165.html
Locked
