> On May 14, 2018, at 2:00 PM, Derek Atkins <de...@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.
Derek, There are 67 GnuCash bugs in Gnome with something in the See Also field: https://bugzilla.gnome.org/buglist.cgi?f1=see_also&list_id=310012&o1=regexp&order=Bug%20Number&product=GnuCash&query_format=advanced&v1=.%2B <https://bugzilla.gnome.org/buglist.cgi?f1=see_also&list_id=310012&o1=regexp&order=Bug%20Number&product=GnuCash&query_format=advanced&v1=.+> The earliest one is https://bugzilla.gnome.org/show_bug.cgi?id=402289 <https://bugzilla.gnome.org/show_bug.cgi?id=402289>, much later than the ones you’ve imported. https://bugzilla.gnucash.org/bugzilla/buglist.cgi?j_top=OR&order=Bug%20Number&query_format=advanced <https://bugzilla.gnucash.org/bugzilla/buglist.cgi?j_top=OR&order=Bug%20Number&query_format=advanced> returns only 103 bugs. Are you sure you imported 105? If possible it would be nice to convert all of the assignees and QA contacts to the pseudo-users (e.g. gnucash-core-ma...@gnucash.bugs <mailto:gnucash-core-ma...@gnucash.bugs>) instead of the many developers who’re no longer working on GnuCash. Attachments aren’t displayed in the browser even when they’re plain text, see https://bugzilla.gnucash.org/bugzilla/attachment.cgi?id=4&action=edit <https://bugzilla.gnucash.org/bugzilla/attachment.cgi?id=4&action=edit>, "The attachment is not viewable in your browser due to security restrictions enabled by your Bugzilla administrator.” I’ll poke at it some more tomorrow. Regards, John Ralls _______________________________________________ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
