Hi. We are having a discussion over at http://wikitravel.org/shared/Talk:Advertising_policy#New_Monetization_Effort_II that is bleeding into the bug fix/features/upgrades area, so I wanted to be sure this is referenced somewhere relevant, like here. I am soliciting for a seasoned WTer to help guide me through the process of sifting for the best next steps to improving the site. I am aware of Road Map and Top Bugs, but it looks like they are not frequently updated either. Any takers on my request? --IBobi 13:38, 22 June 2011 (EDT)
Also, I made a request that someone put together a Top Feature Requests page similar to Top Bugs. I see that this is essentially the function of the Road Map -- yes?IBobi 17:45, 22 June 2011 (EDT)
Hi. I've been informed that the two tech requests on this list are non-starters, and were resolved as "will not pursue" items quite a long time ago. I'll go ahead and remove "Use of Common.css and Common.js" and "Range blocks" from consideration. --IBobi 19:47, 12 July 2011 (EDT)
Oh OK. Make sure you close the tickets itself before removing them from this roadmap. You should state why they are "will not pursue" items, when the decision was made and who actually made the decision before closing them (which you do by changing each tickets category from open feature requests to Finished feature requests).For now, I reverted your edit in this article and left a note about it on your talk page so it can be done in the right order :-) Riggwelter 21:06, 12 July 2011 (EDT)
It would be inappropriate under any circumstances to remove these entries from the nominations page. Regardless of IB's inclination to pursue these feature requests, they are here as community nominations. --PeterTalk 11:11, 13 July 2011 (EDT)
IBobi has suggested that we start a Top feature requests page, like with the Top bugs. I suppose this could be done with a name change from Roadmap to Top feature requests. What do you reckon? Personally, I think that is a good idea. It means moving the page to its new name and revamping it to look something like the Top bugs page. Riggwelter 07:24, 15 July 2011 (EDT)
Following the discussion here, I have added columns for date and deadline. The date column is the date when the ticket was added to Top bugs. The deadline column is for IB and should contain the date when the bug is to be fixed and ticket closed. Riggwelter 07:56, 15 July 2011 (EDT)
I have removed two tickets which had no votes since Sep 23 2009. Please note that the tickets are still open and can be put back if wanted. If someone does that, please remember to vote... Riggwelter 07:56, 15 July 2011 (EDT)
Today the site was down from approximately 10:15am PDT until 5pm PDT, with scattered windows of access in between. We anticipate the site will be stable going forward, but please alert me if you experience any downtime. In the future, when it is possible to post to WT and alert the community to such site issues (for instance when there is scheduled downtime, unlike today), where is the best place/what is the best method to ensure that the community is kept up to date with what's going on?--IBobi 21:26, 16 August 2011 (EDT)
There are a number of items on the Roadmap scheduled for August/September 2011, so with September almost one-third over is there any status update available? If some of the "complex" tasks don't yet have resources available, would there at least be the possibility of getting a DBA to take a look at the database to see if there is anything that might be done to help some of the performance/timeout issues? -- Ryan 01:36, 9 September 2011 (EDT)
The Mediawiki update is being specced out in tech currently, which is great. I'm not sure how long it will take to actually do it, but as soon as they give me a time frame (and scheduled downtime) I'll post it. It is speculated that some of the site issues and tech requests will resolve after this update. As to the remaining site performance issues, I have a meeting scheduled for next week to discuss a possible (*possible*) hardware solution. I will of course keep everyone posted on that. It may necessitate pushing the ETC on some items, but it will mean a potentially major shift forward in how the site performs. I'm hoping for the best.--IBobi 20:19, 9 September 2011 (EDT)
I think most of us will settle for better - there is plenty of scope for that... Best looks a bit much to hope for. Cheers. Pbsouthwood 14:27, 12 September 2011 (EDT)
Thanks for the update IBobi. Please let us know the plans for the upgrade, as well as whether there is any extra info folks here can provide - for example, things like the spam blacklist, the listing tags, User:Evan's RDF code, etc are non-standard Mediawiki features that might require special attention from your team. -- Ryan 16:39, 12 September 2011 (EDT)
I have my doubts about September. Met today with tech and Mediawiki upgrade is very much on the front burner, being specced as we speak, and it's going to be a matter of how difficult our team thinks it will be... but I'm thinking October (hoping not November); and we will likely do the MW update before other major site changes happen. Still looking into smaller bugs/requests.--IBobi 18:40, 12 September 2011 (EDT)
So slow today as to be unusable for editing. A minute to get a diff, or recent changes. I'll try again tomorrow. --Inas 17:19, 22 November 2011 (EST)
Now that we're past 1.15, my impression is that upgrading the software is incremental and *far* easier than the massive 1.11-1.17 upgrade that was just completed (minus remaining bug fixes).
I would like to know, in order to go to my administration and tech people here at IB, what features of 1.18 and 1.19 are being requested for WT, so I can make a case for another upgrade soon.
Additionally, if there is a projection of when 1.2 will be released, and what relevant features it will contain for WT, I'd love to hear about that. Most importantly, anything that helps admins to patrol edits, remediate spam, add content, and general performance improvements. Thank you!--IBobi 14:17, 21 June 2012 (EDT)
The 1.18 new features are here . Especially important ones: Improved directionality support (a headache now), Easily find where to customize interface messages (ditto), New plugin for collapsible elements, and ConfirmEdit extension.
The 1.19 new features are here . Especially important ones: bug fixes. --PeterTalk 14:28, 21 June 2012 (EDT)
Thank you, Peter -- I did see those release notes, but it's nice to have a more WT-centric POV on them. In your opinion, is it worthwhile to hold off on the full 1.20 until it is released and considered stable, or are the 1.18-19 features immediately impactful? —The preceding comment was added by IBobi (talk • contribs) .
I can't comment on new features, but solely from a security and bugfix standpoint it seems like allowing Wikitravel to fall more than two releases behind would be a concern. The 1.17 series is no longer officially supported as of tomorrow (June 22)  and thus will no longer receive security and bug fixes, which should be reason enough to consider upgrading fairly soon. Similarly, if upgrades always involve moving across several releases the upgrade process will be significantly more difficult for your tech team than if the upgrade was just for a single version upgrade. -- Ryan 15:43, 21 June 2012 (EDT)
I think the security issue is a very fair point. Thanks Ryan.--IBobi 17:31, 21 June 2012 (EDT)
Ugh. Good to know. Tech is already investigating how to implement the available patch.--IBobitalkemail 15:05, 17 July 2012 (EDT)
UPDATE -- tech is testing the patch today and tomorrow. Hope to implement this week.--IBobitalkemail 14:14, 18 July 2012 (EDT)
The MW 1.17.2 patch was deployed early this morning Pacific time. Please let me know as soon as possible if it has not addressed the spambot issue and the deletion problem.--IBobitalkemail 13:13, 24 July 2012 (EDT)
The problems persist. I am again having problems with session failure/hijacking as of today. Deleting all cookies and logging out & back in again does resolve the problem, but the last time I did this, I had another session failure within about 10 edits. --PeterTalk 13:52, 26 July 2012 (EDT)
Cache has been blown. Effects of patch should now be propagated to the whole site. Please report if issue persists today or going forward. Thank you,--IBobitalkemail 18:26, 31 July 2012 (EDT)