As anyone who's used Bugzilla in the last few months already knows, Gnome has 
moved their git repositories to a Gitlab instance at gitlab.gnome.org and 
migrated bug tracking for Gnome projects there as well. They've left Bugzilla 
alone for non-Gnome projects like GnuCash but they're closing it to new bugs on 
Sunday, 1 July.

Most users and contributors know that to get ready we've set up a new Bugzilla 
instance at https://bugs.gnucash.org and copied all of the bugs and their 
history and all user accounts. We'll do a final fetch from bugzilla.gnome.org 
at 2018-06-29 22:00:00 UTC (That's tomorrow at 8PM UTC/10PM European Daylight 
Time/4PM US Eastern Daylight Time). We expect to be able to "turn on" 
https://bugs.gnucash.org within a couple of hours. 

The process will be:
* Close bug creation on bugzilla.gnome.org. Unfortunately we can't prevent 
updating already-created bugs, but any changes to bugs on bugzilla.gnome.org 
after this will probably be lost.
* Fetch the latest bug status from bugzilla.gnome.org
* Close all open bugs on bugzilla.gnome.org as "RESOLVED OBSOLETE" with a 
comment pointing to https://bugs.gnucash.org for further discussion. We're 
using RESOLVED OBSOLETE to be consistent with the Gnome project bugs.
* Import the changes to bugs.gnucash.org
* Re-enable updates in the bugzilla code; that's disabled now because imports 
don't work if it's enabled.

User accounts are preserved, but passwords are obviously not preserved. 
Existing bugzilla.gnome.org users should use the "forgot my password" link on 
https://bugs.gnucash.org to get a password reset and to enable their accounts 
after the migration is complete.

Bug CC lists *are* preserved so you will get email notifications for changes to 
bugs that you've commented on or otherwise added yourself to the CC list. 
"Watching" links are *not* preserved so if you were watching another user or 
one of the category users you'll need to reset that in Email Preferences (click 
the Preferences link at the top of the page after you log in).

The category users are:
* gnucash-core-ma...@gnucash.bugs             GnuCash/Backend-SQL, Backend-XML, 
Budgets, Build system, Business, Currency and Commodity, Engine
* gnucash-documentation-ma...@gnucash.bugs    Documentation, Website, 
GnuCash/Translations
* gnucash-general-ma...@gnucash.bugs          GnuCash/General
* gnucash-import-ma...@gnucash.bugs           GnuCash/Import - *, TXF Export
* gnucash-mac-ma...@gnucash.bugs              Packaging/MacOS, GnuCash/MacOS
* gnucash-reports-ma...@gnucash.bugs          GnuCash/Check Printing, Reports
* gnucash-ui-ma...@gnucash.bugs               GnuCash/Regist2, Register, User 
Interface General
* gnucash-win-ma...@gnucash.bugs              Packaging/Windows, GnuCash Windows
* gnucash-all-ma...@gnucash.bugs              All bugs

Since we have the whole bug tracker to ourselves we've created some new 
products and moved some bugs into them:
* GnuCash         continues to collect reports on the application itself.
* Documentation   collects documentation reports
* Packaging       collects reports about the all-in-one Windows and MacOS 
packages that are not about GnuCash application code.
* Website         collects reports about www.gnucash.org.

More information on https://wiki.gnucash.org/wiki/Bugzilla.

Regards,
John Ralls


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

Reply via email to