The first step of the migration is to restrict the access ofmaking any changes on bugzilla.wikimedia.org, leaving it as read-only for everybody except a few people involved in the migration. This will freeze the database that will be migrated to Phabricator. (First Bugzilla goes read-only for everybody except for the import script, and then comes the move. The blocker is set accordingly.)
(I guess first goes read-onlyDuring the migration, and then comes the move. The blocker is set accordingly.)the current https://bugzilla.wikimedia.org will be set in read-only mode and then moved to old-bugzilla.wikimedia.org until further notice.
----
During the migration,After that, Bugzilla users will still be able to log into https://old-bugzilla.wikimedia.org (see T366), view (outdated) tickets, run a search or access their list of votes. the current https://bugzilla.wikimedia.org will be set in read-only mode at old-bugzilla.wikimedia.org until further noticeThey will not be able to edit anything (no comments, no other changes) via browser or via API. Obviously tickets will not be up-to-date as the all the fun continues in Phabricator instead.
This is unrelated to redirecting bugzilla.wikimedia.org/* URLs to Phabricator (T65T40).
People should still be able to view tickets, but not edit anything (no comments, no new accounts, no other changes), preferably by not allowing anybody to log in anymore via browser or via API.
I found http://toolsmiths.blogspot.com/2008/05/making-bugzilla-read-only.html and if I understand correctly, the author's recommendation is:----
I found http://toolsmiths.blogspot.com/2008/05/making-bugzilla-read-only.html and the proposed steps (listed below) work. Same recommendation was given when I asked on https://groups.google.com/forum/#!topic/mozilla.support.bugzilla/aUzv2vNLduo : Make all products in Bugzilla uneditable via these steps:
1) Remove "Open for bug entry" on editproducts.cgi (to not allow creating new tickets).
2) Create a group called "Canstilledit" and make admins members.
3) Use "Edit Group Access Controls" on editproducts.cgi to check the "Canedit" boolean for only that new group "Canstilledit", so "this product will be read-only for any users who are not members of all of the groups with Canedit selected" which would be that one new group.
4) Set "announcehtml" on editparams.cgi to inform everybody that Bugzilla is read-only, that all reports are now in Phabricator, and that there will be an intentional error when trying to edit any tickets in the read-only Bugzilla instance. Potentially mention that Search still works but is obviously not updated, and that people can find the parameters for their searches via "Edit Search" in Bugzilla so they could try to manually emulate that search via [[ https://phabricator.wikimedia.org/maniphest/query/advanced/ | Phabricator's advanced search ]] if similar options are available. Also see T40 for the redirects part.
I've also asked on https://groups.google.com/forum/#!topic/mozilla.support.bugzilla/aUzv2vNLduo if there are better recommendations.:
There is no way to tell Bugzilla "make all tickets read-only which have status RESOLVED" or such> <div id="message" style="text-align: center;">Wikimedia has <a href="https://www.mediawiki.org/wiki/Phabricator/versus_Bugzilla">migrated from Bugzilla to Phabricator</a>. Bug reports should be created and updated in <a href="https://phabricator.wikimedia.org/maniphest">Wikimedia Phabricator</a> instead. If you have not done yet, <a href="https://phabricator.wikimedia.org/auth/start/">create an account</a> in Phabricator and add your Bugzilla email address in Phabricator by <a href="https://www.mediawiki.org/wiki/Phabricator/Help#Creating_your_account">following these instructions</a>. Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Wikimedia Bugzilla you will be shown an intentional error message. Only option is to make certain products in Bugzilla read-only via the workaround explained above.You can still run a search in Bugzilla or access the <a href="https://old-bugzilla.wikimedia.org/page.cgi?id=voting%2Fuser.html">list of tickets you have voted on</a> but bug reports will obviously not be up-to-date in Bugzilla.</div>