[GNC-dev] Bugzilla Migration Status -- phase 2 -- please test

[John Ralls]

The bugs Derek’s imported so far are (which 3 exceptions) from 10 years ago so only the users who were involved in those 103 bugs are in the system and can get a password reset. That will change as he gets comfortable with the imports and does larger ones. 

Browse is broken, searching by component returns “zarro” even if there are bugs with that category.

Regards,
John Ralls


> On May 14, 2018, at 8:56 PM, Adrien Monteleone <adrien.monteleone at lusfiber.net> wrote:
> 
> I suppose you’re still revising things.
> 
> Currently, I see components listed, but no bugs found.
> 
> I also tried a password reset but never received the email.
> 
> Is this only for official developers to test right now, or anyone who has a Gnome Bugzilla account and participated in bug reports?
> 
> Regards,
> Adrien
> 
>> On May 14, 2018, at 4:00 PM, Derek Atkins <derek at ihtfp.com> wrote:
>> 
>> Hi Everyone,
>> 
>> tl;dr: I have a partial migration up and running (~105 / 8588 bugs) and I
>> think my migration script is "complete" -- please test.  Also, please let
>> me know if you know of any bugs that use the see_also field.
>> 
>> Long Version:
>> 
>> As you all know, we use Gnome's bugzilla instance, and they are
>> transitioning to gitlab (soon, like by June).  Since we only used Gnome
>> infrastructure for BZ and nothing else, we decied to migrate to our own BZ
>> instance.  Part of this migration is moving the bug data from Gnome's BZ
>> to our own.  To that end I've been working on a script using
>> Bugzilla::Migrate and the JSON RPC to pull the data from GnomeBZ and then
>> migrate it into our instance.
>> 
>> At this point in time I *BELIEVE* I am migrating all the data we can get. 
>> I think we're ready for the next stage of testing, which is making sure
>> the data has been migrated correctly, nothing is missing (from the
>> migrated data), and that the BZ instance is, effectively "configured".
>> 
>> To that end, please check the bugs that I've imported.  They are early in
>> the sequence (numerically), but three out-of-sequence bugs I pulled in for
>> dependencies and one for attachment testing from early on.   Let me know
>> if you need some specific bug #s to search for.
>> 
>> One thing my data does NOT have is a bug with anytihng in the see_also
>> data.  Does anyone know of any bugs that use that field?
>> 
>> A quite note on user accounts:  Users are created with crandom passwords. 
>> If you made any comments/changes/etc to a bug then you have an account,
>> and should be able to ask for a password reset.  I would ask that right
>> now we make this a read-only test.  We can do write tests soon.
>> 
>> Also note that I will be blowing away the database regularly as we
>> continue testing, so if you do reset your password, it will likely be
>> resert again out from under you in the not too distant future.
>> 
>> Thanks for testing.  If you find any issues please let me know.  Also let
>> me know if you have any questions.
>> 
>> Thanks!
>> 
>> -derek
>> 
>> -- 
>>      Derek Atkins                 617-623-3745
>>      derek at ihtfp.com             www.ihtfp.com
>>      Computer and Internet Security Consultant
>> 
>> _______________________________________________
>> gnucash-devel mailing list
>> gnucash-devel at gnucash.org
>> https://lists.gnucash.org/mailman/listinfo/gnucash-devel
>> 
> 
> 
> _______________________________________________
> gnucash-devel mailing list
> gnucash-devel at gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-devel