gnucash-htdocs master: Announce Bugzilla Migration

Thu Jun 28 19:52:42 EDT 2018

Updated	 via  https://github.com/Gnucash/gnucash-htdocs/commit/6e9892ca (commit)
	from  https://github.com/Gnucash/gnucash-htdocs/commit/b8cdb953 (commit)



commit 6e9892ca0d33d2fc3bd995e09462124b98278f56
Author: John Ralls <jralls at ceridwen.us>
Date:   Thu Jun 28 16:52:20 2018 -0700

    Announce Bugzilla Migration

diff --git a/develdocs.phtml b/develdocs.phtml
index b743c3c..62925d6 100644
--- a/develdocs.phtml
+++ b/develdocs.phtml
@@ -66,7 +66,7 @@ include("externals/menu.phtml");
 </div>
 <p class="justify"><?php echo T_("Get a copy of the documentation source as described above and start making changes. When you are satisfied with your changes you can create a patch by running the following command in the base directory of the documentation (usually gnucash-docs, unless you renamed it):");?></p>
 <pre class="command">git diff > my-patch-name.patch</pre>
-<p class="justify"><?php echo T_("Next attach your patch to a bug report against the documentation component for the <span class=\"gnucash\">GnuCash</span> project in <a href='https://bugzilla.gnome.org/'>Gnome's bugzilla database</a> and send an email to <a href='mailto:gnucash-devel at gnucash.org'>gnucash-devel</a> mailing list to inform other developers on your work. See also <a href='https://wiki.gnucash.org/wiki/Bugzilla'>GnuCash' wiki page on bugzilla</a> for more details about patch submission.");?></p>
+<p class="justify"><?php echo T_("Next attach your patch to a bug report against the documentation component for the <span class=\"gnucash\">GnuCash</span> project in <a href='https://bugs.gnucash.org/'>Gnome's bugzilla database</a> and send an email to <a href='mailto:gnucash-devel at gnucash.org'>gnucash-devel</a> mailing list to inform other developers on your work. See also <a href='https://wiki.gnucash.org/wiki/Bugzilla'>GnuCash' wiki page on bugzilla</a> for more details about patch submission.");?></p>
 <div class="dialog note">
 <p class="justify"><?php echo T_("<b>NOTE:</b> It used to be ok also to send your patch directly to the gnucash-devel list. This is discouraged now, as a patch is easily forgotten between the many list discussions. Attach patches to bugs in Bugzilla instead (either an existing bug or a new one). If you insist on sending a patch to gnucash-devel, it should be attached, not inlined.");?></p>
 <p class="justify"><?php echo T_("Please let other writers know which section you wish to tackle. Please forward this to <a href='mailto:gnucash-devel at gnucash.org'>gnucash-devel</a> so that people can say 'hey I'm doing that already' or 'go ahead and do it'.");?></p>
@@ -79,7 +79,7 @@ include("externals/menu.phtml");
 <h2 class="featuretitle"><?php echo T_("Reviewers");?></h2>
 </div>   
 <p class="justify"><?php echo T_("Get a copy of the documentation source as described above and start commenting on it.");?></p>
-<p class="justify"><?php echo T_("The best way of retaining comments about docs in an easy to find way for everyone would be to use <a href='https://bugzilla.gnome.org/'>bugzilla.gnome.org</a> to file the bugs under documentation. This can also be done using bug-buddy.");?></p>
+<p class="justify"><?php echo T_("The best way of retaining comments about docs in an easy to find way for everyone would be to use <a href='https://bugs.gnucash.org/'>bugs.gnucash.org</a> to file the bugs under documentation. This can also be done using bug-buddy.");?></p>
 </div>
 
 </div>
diff --git a/news/180628-Bugzilla Migration.news b/news/180628-Bugzilla Migration.news
new file mode 100644
index 0000000..629fb97
--- /dev/null
+++ b/news/180628-Bugzilla Migration.news	
@@ -0,0 +1,38 @@
+<h2>Bugzilla Migration 29 June 2018 at 20:00 UTC</h2>
+<p>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.</P>
+
+<p>Most users and contributors know that to get ready we've set up a new Bugzilla instance at <a href="https://bugs.gnucash.org">https://bugs.gnucash.org</a> 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. </p>
+
+<p>The process will be:
+<ul>
+<li>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.</li>
+<li>Fetch the latest bug status from bugzilla.gnome.org</li>
+<li>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.</li>
+<li>Import the changes to bugs.gnucash.org</li>
+<li>Re-enable updates in the bugzilla code; that's disabled now because imports don't work if it's enabled.</li>
+</ul></p>
+<p>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.</p>
+
+<p>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).</p>
+
+<p>The category users are:
+<table style="width: 50%;">
+<tr style="width: 30%;"><td style="width: 50%;">gnucash-core-maint at gnucash.bugs</td><td>GnuCash/Backend-SQL, Backend-XML, Budgets, Build system, Business, Currency and Commodity, Engine</td></tr>
+<tr><td>gnucash-documentation-maint at gnucash.bugs</td><td>Documentation, Website, GnuCash/Translations</td></tr>
+<tr><td>gnucash-general-maint at gnucash.bugs</td><td>GnuCash/General</td></tr>
+<tr><td>gnucash-import-maint at gnucash.bugs</td><td>GnuCash/Import - *, TXF Export</td></tr>
+<tr><td>gnucash-mac-maint at gnucash.bugs</td><td>Packaging/MacOS, GnuCash/MacOS</td></tr>
+<tr><td>gnucash-reports-maint at gnucash.bugs</td><td>GnuCash/Check Printing, Reports</td></tr>
+<tr><td>gnucash-ui-maint at gnucash.bugs</td><td>GnuCash/Regist2, Register, User Interface General</td></tr>
+<tr><td>gnucash-win-maint at gnucash.bugs</td><td>Packaging/Windows, GnuCash Windows</td></tr>
+<tr><td>gnucash-all-maint at gnucash.bugs</td><td>All bugs</td></tr>
+</table></p>
+<p>Since we have the whole bug tracker to ourselves we've created some new products and moved some bugs into them:
+<table style="width: 50%;">
+<tr style="width: 20%;"><td>GnuCash</td><td style="width: 75%;">continues to collect reports on the application itself.</td></tr>
+<tr><td>Documentation</td><td>collects documentation reports</td></tr>
+<tr><td>Packaging</td><td>collects reports about the all-in-one Windows and MacOS packages that are not about GnuCash application code.</td></tr>
+<tr> <td>Website</td><td>collects reports about www.gnucash.org.</td></tr>
+</table></p>
+<p>More information in <a href="https://wiki.gnucash.org/wiki/Bugzilla">the Wiki</a>.
+</p>
\ No newline at end of file



Summary of changes:
 develdocs.phtml                     |  4 ++--
 news/180628-Bugzilla Migration.news | 38 +++++++++++++++++++++++++++++++++++++
 2 files changed, 40 insertions(+), 2 deletions(-)
 create mode 100644 news/180628-Bugzilla Migration.news

