Last modified: 2014-10-11 16:50:38 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 65005 - (hackathon2014) Wikimedia Hackathon Zürich 2014
(hackathon2014)
Wikimedia Hackathon Zürich 2014
Status: RESOLVED WORKSFORME
Product: Wikimedia
Classification: Unclassified
General/Unknown (Other open bugs)
wmf-deployment
All All
: Immediate enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
https://www.mediawiki.org/wiki/Z%C3%B...
:
Depends on: 65134 5451 13250 28569 34153 34410 42634 48672 50335 51505 52541 55265 58970 62342 62362 62909 63269 64758 64788 64790 64928 64960 65003 65037 65060 65067 65068 65075 65120 65122 65135 65155 65157 65162 65181
Blocks: tracking
  Show dependency treegraph
 
Reported: 2014-05-07 15:53 UTC by Maarten Dammers
Modified: 2014-10-11 16:50 UTC (History)
7 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Maarten Dammers 2014-05-07 15:53:30 UTC
Tracker for bugs people work on and fix at the Wikimedia Hackathon
Zürich 2014 https://www.mediawiki.org/wiki/Z%C3%BCrich_Hackathon_2014
Comment 1 Andre Klapper 2014-05-07 16:03:27 UTC
Note: Everybody who has fixed/closed a bug report should enter
      hackathon2014
(or instead the bug number 65005)
in the "Blocks:" field of that bug report.
Comment 2 Greg Grossmeier 2014-05-09 09:31:57 UTC
Setting importance for the weekend.
Comment 3 James Forrester 2014-05-15 17:21:01 UTC
Should this bug be closed, and remaining unfixed dependencies removed from it?
Comment 4 James Forrester 2014-05-16 15:14:43 UTC
(In reply to James Forrester from comment #3)
> Should this bug be closed, and remaining unfixed dependencies removed from
> it?

Replying to myself: Yes. Done.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links