Closed Bug 600834 Opened 12 years ago Closed 11 years ago
Touch 2010 on staging server
We need to go through the MDC test plan on the staging server once the upgrade to 2010 is done. Odds are decent that we will find skin changes that need to be made.
Assignee: jeremy.orem+bugs → mozwebqa
Depends on: 600833
The test plan is here, and Raymond is running through it now: https://wiki.mozilla.org/QA/Execution/Web_Testing/MDC/Test_Plan
Depends on: 605646
Depends on: 605667
(In reply to comment #2) > Bug 605549 and bug 605645 should block, not depend on, this bug. Raymond ^^^
This isn't an IT bug right?
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → INVALID
This is now ready for testing in preparation for deployment.
Assignee: mozwebqa → mozbugs.retornam
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
(In reply to comment #5) > This is now ready for testing in preparation for deployment. is it hosted on https://developer-stage9.mozilla.org or https://developer-stage.mozilla.org
https://developer-stage.mozilla.org is the MindTouch 2010 update that this bug is about testing. https://developer-stage9.mozilla.org is for staging minor updates to the MindTouch 9.x install we're currently running, and isn't the focus of this bug.
I'm uncomfortable with the level of potential risk that doing an upgrade could pose, given the QA resources we have, as we're behind with the Firefox 4-associated projects, as it is; this can wait until after we ship, right?
I agree - can this wait till post Fx4?
Ugh. I soooo wish I could say "no", but yeah, it can wait until after Firefox 4. I don't like it though. I'd personally rather have Firefox 4 wait. :)
Component: Server Operations → Mozmill Tests
Product: mozilla.org → Mozilla QA
QA Contact: mrz → mozmill-tests
Version: other → unspecified
Why Mozmill? I think that should go to the devmo component.
Assignee: mozbugs.retornam → nobody
Component: Mozmill Tests → Website
Product: Mozilla QA → Mozilla Developer Network
QA Contact: mozmill-tests → website
A major security flaw has been discovered in MindTouch that extends all the way back to the version we're using now. We need to get upgraded to the latest version ASAP to get rid of it, as the fix will not be backported.
Severity: normal → blocker
What's the security flaw?
I don't have details, but it turns out there's a way to mitigate the problem -- and our configuration is already set up that way, so we're okay. That said, it's still time to get the staging server into QA so we can update.
What version is staging running, and is it ready for QA? https://developer-stage.mozilla.org/Special:About doesn't list its version. Also, last time we were asked to test, there were configuration issues with signup, etc.
Looks like we're behind by a few patches again. I'll file a ticket that blocks this one asking IT to update us. Configuration wise, I don't know of any remaining outstanding issues.
OK. Looks like we're updated and ready for testing. I've been poking around and things seem to be working as far as I can tell.
Raymond, while Sheppy tests MindTouch can you make a pass on the django site at developer-stage.mozilla.org so we know MindTouch 10 doesn't break any of the django-dekiwiki integration points? Auth, landing pages, demo studio, etc. Thanks.
Do we know when QA will have time for this testing? I'd like to know when to expect that testing to occur.
Hi Eric I will be testing the upgrade on staging from today till end of day Friday 04/1 and mark any bugs I find as a blocker to this bug.
11 years ago
Depends on: 652688
I asked MindTouch to look at our comments on bug 652190. We're back to an error on the activitydashboard tab. :(
I'm very excited to see all the dependencies closed here.
Do we know - who did the MindTouch 2010 upgrade in staging? We want to try to push it to production this week and it would help to CC whoever upgraded staging.
Status: REOPENED → RESOLVED
Closed: 12 years ago → 11 years ago
Resolution: --- → FIXED
Component: Website → Landing pages
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.