AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Bugzilla wikimedia12/21/2023 The old wiki is still accessible at but I believe it's read only now, as we should be using. With the introduction of Labs, ops decided that it would be good to merge the labs wiki and wikitech together, and so after a long time waiting they finally merged the two wikis at the beginning of this month. The problem with this is that the old wikitech wiki was rarely updated or maintained (it's on MediaWiki 1.19.2 right now), and it also had restricted editing. Wikitech is a wiki that is outside of the usual Wikipedia cluster so that if the site goes down, tech staff still have that wiki up to be able to access technical documentation etc. Yeah a couple of people have brought this up so a full explanation for anyone else, with extra background info: > current database and estimate when we can upgrade? > Is there a status update about this bug? Has Martin been able to assess the > wikitech and is sending password details directly to Martin. > requests can take a couple of weeks to process). > I chased this up with CT to get this request fast tracked (sometimes these And if there are further good reasons why an OTRS upgrade blocks development work, I kindly request to bring them up in Bugzilla.īoth helps everybody to get a better impression on how severe and urgent the OTRS upgrade request is (how many and which issues would get solved by it), and would lead to reevaluating this request.Īgain: I don't see this as a "blocker" based on what's known. If there are more unreported issues with OTRS they are extremely welcome to be reported in Bugzilla (bonus points for finding out if an OTRS software upgrade would influence them and marking them as depending on bug 22622 - upstream bugtracker is at for queries). This does not mean that we would not vastly benefit from an OTRS update to make life of our community in OTRS easier. I don't think this justifies "blocker" severity ("blocks development work", see ) yet, so I propose resetting this to "major". Out of 15 open tickets (some of them unresolved upstream issues, two local configuration issues) there are 2 known problems (see "Blocks" field) that would get solved by upgrading. I've just retriaged all open OTRS tickets in Bugzilla. > &query_format=advanced&component=OTRS&product=Wikimedia This would need to be discussed with CT first. Daniel (among others) seem reasonably comfortable working with Perl for Bugzilla. You will need an ops point of contact too, I believe this was going to be Jeff Green originally, however we're getting close to fundraising season, so I'm not sure how much time he would have available. I know Ops were keen to get this also puppetied, but I don't think this is a blocker from the point of upgrading. Probably some testing on our side with our current OTRS usersĪnd after that, schedule some maintenance/downtime for our current OTRS install, update files, update the database and make it live again. Next, a test install on the WMF cluster, db upgrade etc. Tell "us" (probably better on the RT ticket) what you need A copy of our current otrs database and a copy of the OTRS files as current is?įrom there, I suppose you can do a test upgrade locally, and see if you can create updates for our "patches" that are in SVN. > Update, I resent the NDA to Philippe now. PS: In case you need more details to the security issues, see !/advisory/ZSA-2012-01 and !/advisory/ZSA-2012-02 How can we proceed with the OTRS 3.1 upgrade? Who is the contact person? O Kernel/Modules/AgentTicketAttachment.pm with version 1.22.2.7 O Kernel/Modules/CustomerTicketAttachment.pm with version 1.17.2.7 Update, I resent the NDA to Philippe now.
0 Comments
Read More
Leave a Reply. |