Re: Planned MAJOR OUTAGE: Thursday 08th of February, 17:00 - 19:00 UTC

[Derek Atkins]

John Ralls  writes:

[snip]
> We may want to pre-process the db dump to have sequential
> numbers. It’s something to think about.

I don't think we would want to renumber our existing bugs.  I think it's
useful to keep the current numbers, as we already reference e.g. Bug
#xxx in the code, in commit messages, PRs, etc.  Yes, the URL will
change from bugzilla.gnome.org to bugzilla.gnucash.org, but the rest of
the URL (and most importantly #) can remain.

> 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.

I thought all those entries were DB settings, not necessarily code
changes.  But I've never set up BZ (or any other tracker, short of Trac,
but that won't scale to our needs IMHO).  It would be a learning
experience.

> 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 instance.

Agreed -- one dump to play with the conversion.  And then a final dump
to actually swap over.  The hardest part will be getting the gnome BZ
people to drop us a dump at all.

> 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.

I agree, GC3 is top priority as a team.  On the other hand, *I*
personally have very little hands-on involvement in that process, so I
*could* be working on the bug tracker simultaneously to you all working
o GC3.  Of course I wouldn't want to do the final switchover until I've
moved, but some of the initial legwork can happen sooner.

The only "rush" is time availability to plan to BZ move (either to our
own BZ instance, or to something else) -- and making sure we have the
time to do it before GNOME shuts it down sometime in the next 12-18
months, or whenever they do.  I don't want to get a "we're shutting down
in 30 days" email and not have a solid, tested plan in place.

> Regards,
> John Ralls

-derek

-- 
   Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
   Member, MIT Student Information Processing Board  (SIPB)
   URL: http://web.mit.edu/warlord/PP-ASEL-IA N1NWH
   warl...@mit.eduPGP key available
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: Planned MAJOR OUTAGE: Thursday 08th of February, 17:00 - 19:00 UTC

[Geert Janssens]

Op donderdag 15 februari 2018 05:08:37 CET schreef John Ralls:
> 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 instance.
> 
> 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.
> 
Agreed. By that time Gnome will also have some more hands on experience with 
their gitlab bugtracker, which may bring some additional insights.

GC3 is top priority now.

Geert


___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: Planned MAJOR OUTAGE: Thursday 08th of February, 17:00 - 19:00 UTC

[Derek Atkins]

It might take that long to get a db dump.  ;-)
But yes, you're right.

-derek
Sent using my mobile device. Please excuse any typos.



On February 14, 2018 8:37:55 PM John Ralls  wrote:





On Feb 14, 2018, at 8:10 AM, Derek Atkins  wrote:

John Ralls  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. ;-)

Regards,
John Ralls

___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel



___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: Planned MAJOR OUTAGE: Thursday 08th of February, 17:00 - 19:00 UTC

[John Ralls]

> On Feb 14, 2018, at 8:10 AM, Derek Atkins  wrote:
> 
> John Ralls  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. ;-)

Regards,
John Ralls

___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Fwd: Re: Planned MAJOR OUTAGE: Thursday 08th of February, 17:00 - 19:00 UTC

[John Ralls]

> Begin forwarded message:
> 
> Date: Fri, 9 Feb 2018 12:44:46 +0100
> From: Andrea Veri <a...@gnome.org <mailto:a...@gnome.org>>
> To: infrastructure-annou...@gnome.org 
> <mailto:infrastructure-annou...@gnome.org>
> Cc: desktop-devel-list <desktop-devel-l...@gnome.org 
> <mailto:desktop-devel-l...@gnome.org>>,  Foundation
>   List <foundation-l...@gnome.org <mailto:foundation-l...@gnome.org>>
> Subject: Re: Planned MAJOR OUTAGE: Thursday 08th of February, 17:00 -
>   19:00 UTC
> Message-ID:
>   <camfty2pxuzqpbiwomqtpb8nzrssmgk406zmws2iskokmgyl...@mail.gmail.com 
> <mailto:camfty2pxuzqpbiwomqtpb8nzrssmgk406zmws2iskokmgyl...@mail.gmail.com>>
> Content-Type: text/plain; charset="UTF-8"
> 
> While the move was overall successful one of the hosts has been found
> having an hardware failure and requires its mainboard to be replaced.
> The part will be replaced today between 14 - 15 UTC. The affected
> services that will have a downtime are:
> 
> bugzilla.gnome.org <http://bugzilla.gnome.org/>
> paste.gnome.org <http://paste.gnome.org/>
> etherpad.gnome.org <http://etherpad.gnome.org/>
> id.gnome.org <http://id.gnome.org/>
> opw.gnome.org <http://opw.gnome.org/>
> 
> Thanks,
> 

___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel