Last modified: 2012-09-19 20:58:43 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T40803, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 38803 - MediaWiki bugs to be fixed for 1.20wmf9 deployment (tracking)
MediaWiki bugs to be fixed for 1.20wmf9 deployment (tracking)
Status: RESOLVED DUPLICATE of bug 38865
Product: Wikimedia
Classification: Unclassified
General/Unknown (Other open bugs)
unspecified
All All
: Unprioritized blocker (vote)
: ---
Assigned To: Sam Reed (reedy)
:
Depends on: 39296
Blocks:
  Show dependency treegraph
 
Reported: 2012-07-29 21:20 UTC by Krinkle
Modified: 2012-09-19 20:58 UTC (History)
3 users (show)

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


Attachments

Description Krinkle 2012-07-29 21:20:32 UTC
Like bug 36974 and bug 37346. To track bugs in MediaWiki core and MediaWiki
extensions that should be fixed before deployment.
Comment 1 Phillip Patriakeas 2012-07-30 02:28:27 UTC
Stupid question, maybe, but why doesn't there seem to be a tracking bug for the pre-WMF-deployment bug fix tracking bugs?
Comment 2 Rob Lanphier 2012-07-30 20:01:39 UTC
Assigning to Sam, since we'll need him to check this list prior to a deployment.
Comment 3 Rob Lanphier 2012-07-30 20:02:25 UTC
Phillip, I'm not sure I understand your question.  1.20wmf9 hasn't been branched yet, so this may actually be the bug you're looking for.
Comment 4 Alex Monk 2012-07-30 20:10:59 UTC
I think Phillip wants to know why there isn't a single tracking bug for all these "bugs to be fixed for deployment" tracking bugs.
Comment 5 Phillip Patriakeas 2012-07-30 20:11:59 UTC
(In reply to comment #4)
> I think Phillip wants to know why there isn't a single tracking bug for all
> these "bugs to be fixed for deployment" tracking bugs.

Yeah, that's what I'm after. Sorry I wasn't more clear.
Comment 6 Sam Reed (reedy) 2012-07-30 20:52:20 UTC
Because no one created one. There is now bug 38865 for that
Comment 7 Sam Reed (reedy) 2012-07-30 22:33:23 UTC
(In reply to comment #2)
> Assigning to Sam, since we'll need him to check this list prior to a
> deployment.

As bug 38801 isn't actually happening on the cluster, and has only one person experiencing it, it's certainly not a blocker for the time being
Comment 8 Sam Reed (reedy) 2012-08-20 13:38:35 UTC
Deployed
Comment 9 Krinkle 2012-09-19 18:07:04 UTC

*** This bug has been marked as a duplicate of bug 38865 ***

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


Navigation
Links