The thing is that a db dump will be a snapshot, so what we want to do is have
BZ set up and ready to go on code, then get the Gnome bug team to turn off our
BZ instance there and send us a dump that we can immediately load and then turn
on our instance.
We may want to pre-process the db dump to have sequential numbers. It’s
something to think about.
We also need to think about what BZ we’re going to use. Gnome forked BZ
somewhere around version 3 and have made some modifications to suit their
needs. We can take that fork and tweak it for our use (just an e.g. it wouldn’t
make a lot of sense for us to have “Not Gnome” as a reason for resolving a bug)
or we can get the current Mozilla BZ and use that, recognizing that we’ll
probably need to tweak the db dump from Gnome to get it to load.
So a modification to my lead: We need two dumps, a preliminary one to test with
while we get our BZ set up and then a final one that turns off the Gnome
We might want to look at what else is available before settling on BZ. In
addition to you getting your new house done, Geert, Frank, and I need to focus
on getting GC3 out the door, so let’s defer further discussion of this until
later this spring. There are no signs on the Gnome lists that BZ is going to be
shut down any time soon, so there’s no real rush.
> On Feb 14, 2018, at 5:41 PM, Derek Atkins <warl...@mit.edu> wrote:
> It might take that long to get a db dump. ;-)
> But yes, you're right.
> Sent using my mobile device. Please excuse any typos.
> On February 14, 2018 8:37:55 PM John Ralls <jra...@ceridwen.us> wrote:
>>> On Feb 14, 2018, at 8:10 AM, Derek Atkins <warl...@mit.edu> wrote:
>>> John Ralls <jra...@ceridwen.us> writes:
>>>> I think the only thing there that will impact us is bugzilla.
>>> We should really start thinking about running our own BZ instance,
>>> assuming we can get a DB Dump from GNOME.
>> Maybe, but not until you’re into your new house. ;-)
>> John Ralls
>> gnucash-devel mailing list
gnucash-devel mailing list