Hi everybody!
More than six months ago, Wikimedia migrated its bug report management from Bugzilla to Phabricator. At the same time, Bugzilla was turned read-only (but still allowed users to log in to access and manually migrate votes or saved searches) and moved to the address old-bugzilla.wikimedia.org.
Before that migration, users were asked to join Phabricator and were made aware of required steps and limitations [1]. This was done via a banner on top of Bugzilla, emails on wikitech-l@, announcements on en.wp Village Pump, and two emails to all Bugzilla users who had logged in since October 2013 [2].
Now after everybody had more than six months to switch to Phabricator, old-bugzilla.wikimedia.org is planned to get switched off on June 22nd [3] (as keeping Bugzilla running requires maintenance like applying security updates).
Thanks to John and Daniel, a static HTML version of old-bugzilla exists at https://static-bugzilla.wikimedia.org [4]. It allows to still access those historical Bugzilla reports and the related history/activity.
Please note that you can still claim the activity of your Bugzilla account imported into Phabricator [5] after switching off old-bugzilla, as this functionality does not rely on old-bugzilla being available.
I'd like to thank John & Daniel for all their work creating static-bz!
Cheers, andre
[1] https://www.mediawiki.org/wiki/Phabricator/versus_Bugzilla#Missing_data [2] https://phabricator.wikimedia.org/T618 [3] https://phabricator.wikimedia.org/T95184#1327072 [4] https://phabricator.wikimedia.org/T85140 [5] https://www.mediawiki.org/wiki/Phabricator/Help#Claiming_your_previous_Bugzi...
On Mon, Jun 8, 2015 at 11:13 AM, Andre Klapper aklapper@wikimedia.org wrote:
Thanks to John and Daniel, a static HTML version of old-bugzilla exists at https://static-bugzilla.wikimedia.org [4]. It allows to still access those historical Bugzilla reports and the related history/activity.
The few times I've really needed to use old-bugzilla were because old attachments weren't always imported to Phab, which I see is https://phabricator.wikimedia.org/T78747. In particular, this might be a problem for restricted-access bugs.
Hi,
On 06/08/2015 08:13 AM, Andre Klapper wrote:
Now after everybody had more than six months to switch to Phabricator, old-bugzilla.wikimedia.org is planned to get switched off on June 22nd [3] (as keeping Bugzilla running requires maintenance like applying security updates).
Do we have usage statistics on how many people are still using old-bugzilla? I still use it frequently for searching for example.
Will old-bugzilla redirect to static-bugzilla?
-- Legoktm
On Mon, 2015-06-08 at 09:48 -0700, Legoktm wrote:
Do we have usage statistics on how many people are still using old-bugzilla? I still use it frequently for searching for example.
Only data that I am aware of is https://phabricator.wikimedia.org/T86859#1182758
(And yes, Phabricator's "Search can be improved" as stated in https://www.mediawiki.org/wiki/Phabricator/versus_Bugzilla#Considerations )
andre
I'd like to thank John & Daniel for all their work creating static-bz!
+1
From: aklapper@wikimedia.org To: wikitech-l@lists.wikimedia.org Date: Mon, 8 Jun 2015 17:13:08 +0200 Subject: [Wikitech-l] old-bugzilla.wikimedia.org to be switched off in favor of static-bugzilla
Hi everybody!
More than six months ago, Wikimedia migrated its bug report management from Bugzilla to Phabricator. At the same time, Bugzilla was turned read-only (but still allowed users to log in to access and manually migrate votes or saved searches) and moved to the address old-bugzilla.wikimedia.org.
Before that migration, users were asked to join Phabricator and were made aware of required steps and limitations [1]. This was done via a banner on top of Bugzilla, emails on wikitech-l@, announcements on en.wp Village Pump, and two emails to all Bugzilla users who had logged in since October 2013 [2].
Now after everybody had more than six months to switch to Phabricator, old-bugzilla.wikimedia.org is planned to get switched off on June 22nd [3] (as keeping Bugzilla running requires maintenance like applying security updates).
Thanks to John and Daniel, a static HTML version of old-bugzilla exists at https://static-bugzilla.wikimedia.org [4]. It allows to still access those historical Bugzilla reports and the related history/activity.
Please note that you can still claim the activity of your Bugzilla account imported into Phabricator [5] after switching off old-bugzilla, as this functionality does not rely on old-bugzilla being available.
I'd like to thank John & Daniel for all their work creating static-bz!
Cheers, andre
[1] https://www.mediawiki.org/wiki/Phabricator/versus_Bugzilla#Missing_data [2] https://phabricator.wikimedia.org/T618 [3] https://phabricator.wikimedia.org/T95184#1327072 [4] https://phabricator.wikimedia.org/T85140 [5] https://www.mediawiki.org/wiki/Phabricator/Help#Claiming_your_previous_Bugzi...
-- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
On 8 Jun 2015, at 16:13, Andre Klapper aklapper@wikimedia.org wrote:
Thanks to John and Daniel, a static HTML version of old-bugzilla exists at https://static-bugzilla.wikimedia.org [4]. It allows to still access those historical Bugzilla reports and the related history/activity.
I noticed that it serves content in two places now: https://static-bugzilla.wikimedia.org/show_bug.cgi?id=1 https://static-bugzilla.wikimedia.org/show_bug.cgi?id=1 https://static-bugzilla.wikimedia.org/show_activity.cgi?id=1 https://static-bugzilla.wikimedia.org/show_activity.cgi?id=1 and: https://static-bugzilla.wikimedia.org/bug1.html https://static-bugzilla.wikimedia.org/bug1.html https://static-bugzilla.wikimedia.org/activity1.html https://static-bugzilla.wikimedia.org/activity1.html
Can these be de-duplicated for search indexing? Either by 301 redirecting, or by using a rel=canonical HTTP Link-headers https://support.google.com/webmasters/answer/139066 https://support.google.com/webmasters/answer/139066
I suggest we consider the show_bug/show_activity urls as canonical to the public. The html files are secondary/internal, no need to expose those directly.
https://static-bugzilla.wikimedia.org/show_activity.cgi?id=1 https://static-bugzilla.wikimedia.org/show_activity.cgi?id=1 should not become a redirect.
On 8 Jun 2015, at 17:48, Legoktm legoktm.wikipedia@gmail.com wrote:
Will old-bugzilla redirect to static-bugzilla?
+1
Will bugzilla also redirect to static-bugzilla? E.g. https://bugzilla.wikimedia.org/show_activity.cgi?id=1 https://old-bugzilla.wikimedia.org/show_activity.cgi?id=1
should both 301 redirect to https://static-bugzilla.wikimedia.org/show_activity.cgi?id=1
All other bugzilla endpoints not covered by show_bug/show_activity I assume will become 404. (Seems acceptable). Currently they are 301 redirect to old-bugzilla.
-- Krinkle
wikitech-l@lists.wikimedia.org