Re: [Gramps-devel] gramps50 and 5.0.0

[Paul F. <pf....@gm...>]

On 5/22/17, Nick Hall <ni...@gr...> wrote:
> On 21/05/17 18:15, Paul Franklin wrote:
>> On 5/7/17, Nick Hall<ni...@gr...>  wrote:
>>> Unfortunately, I have just found a problem with SQL transactions.  Some
>>> of the unit tests which use an in-memory sqlite database are failing on
>>> my development machine.
>> Do you have any news?
>>
>> Is 10038 the only problem [1]?  Do you know what you will do?
>
> I haven't had time to look at it further yet.
>
>>
>> Is that the only DB-API problem which needs fixing?
>
> There may be more.  I need to go through the roadmap.
>
>>
>> Are you going to fix it before you make the gramps50 branch?
>
> Only if the fix is easy.
>
>>
>> Thanks.
>>
>>
>> [1]https://gramps-project.org/bugs/view.php?id=10038#c51773
>>
>
>

Thanks for the update.

I will remind you that a year ago, 16 Apr 2016, you said:

"A sensible alternative would be to release v4.3 in June, with BSDDB as
the default database."

If you don't have time now to investigate -- and fix -- all the
DB-API problems, I will again argue that releasing a 4.3.0
in a month or so, with the DB-API stuff deleted or whatever,
still makes sense to me.  That's what I would have done.

That would get a new gramps out there, with all of the features
and new things which have been added, while removing any
pressure for you to come up with the time which you need to
fix the DB-API bugs and get a 5.0.0 release into shape.

I hope you will seriously consider that alternative.

I said back then that "I don't like the idea of doing major
development work so close to a release time" and I still feel
that way.

Thank you.




---------- Forwarded message ----------
From: Nick Hall <ni...@gr...>
Date: Sat, 16 Apr 2016 15:25:25 +0100
Subject: Re: [Gramps-devel] Preparation for Gramps 5.0
To: gra...@li...

Paul,

A sensible alternative would be to release v4.3 in June, with BSDDB as
the default database.

The Select API / QuerySet interface should also be removed.  As I have
already mentioned, agreement was never reached on this.

Efficient select functionality could then be fully integrated into the
filters for a release of v5.0 in June 2017.


Nick.


On 13/04/16 05:52, Paul Franklin wrote:
> I am totally against making such a major change so late in the
> cycle for 5.0.
>
> If you wanted to propose making DB-API the default, instead
> of BSDDB, you should have proposed doing that last July, and
> if it was then agreed upon -- last July -- there would have been
> almost a year of testing, for instance on Windows.
>
> Unless I'm wrong this will be the first gramps release where it
> is even >possible< to have a choice of second type of database.
> I don't think making it the default is the right thing to do, right now.
>
> Why not have a discussion -- right now -- as to whether it should
> become the default when 5.1 is released (in July 2017?)?  If that
> is decided upon, we can announce when we release 5.0 that it
> is now possible and that we encourage all (brave? power user?)
> users who want to try  it, to try it -- and perhaps suggest making
> frequent (daily?) gramps XML backups as they go along.
>
> I don't like the idea of doing major development work so close
> to a release time.
>
> We should be thinking about our users, not our coding.