180
edits
Support/TikiWikiUpgrade: Difference between revisions
Jump to navigation
Jump to search
→James: some notes about sumo_only
(→James) |
MarcLaporte (talk | contribs) (→James: some notes about sumo_only) |
||
| Line 94: | Line 94: | ||
sumo_only is the group of changes that we need to maintain during the syncs. Several of those are template changes, but things in sumo_triage or tiki_triage can also end up in sumo_only, and this is only the first ~1/4th of the bugs to triage. | sumo_only is the group of changes that we need to maintain during the syncs. Several of those are template changes, but things in sumo_triage or tiki_triage can also end up in sumo_only, and this is only the first ~1/4th of the bugs to triage. | ||
===Notes from Marc=== | |||
When we made the categories, (sumo_only, tiki_bug, etc.), our goal was to evaluate how much work it was to upgrade. sumo_only is defined as: "Stuff that is related to the administration/maintenance of the SUMO website that can't really be upstreamed". So for us, that was stuff for which there was almost no work, work which is necessary/implicit anyway (with or without the upgrade), or that was included in a meta-bug. | |||
Perhaps we should further categorize things to get a better picture. For example: | |||
1- sumo_template -> sumo-specific templates that shouldn't be upstreamed (this could include minor features that are trivial to maintain). There will be work to upgrade to Tiki4, but fairly easy to manage and we have two volunteers (the two guys that redesigned Tiki themes in Tiki3). | |||
*[https://bugzilla.mozilla.org/show_bug.cgi?id=442312 SUMO links to php-test blog.mozilla.com] | |||
*[https://bugzilla.mozilla.org/show_bug.cgi?id=399749 Forums link in sidebar goes nowhere sometimes] | |||
*[https://bugzilla.mozilla.org/show_bug.cgi?id=442321 Use https for links to Bugzilla and AMO in header] | |||
2- sumo_feature -> Sumo_specific customization that can't be upstreamed and is not trivial to maintain, like a hardware-specific config. Ex.: SUMO rewrite rules, in-product help. Here, we should evaluate the meta-bug in its current global state and estimate porting to Tiki4 effort. Less work than the first time, but it can be significant if it touches somewhere where Tiki code changed a lot since 1.10. | |||
*[https://bugzilla.mozilla.org/show_bug.cgi?id=412266 Create separate landing page for in-product help] | |||
*[https://bugzilla.mozilla.org/show_bug.cgi?id=489910 Update .htaccess rules to handle firefox-f1 and firefox-osxkey] | |||
3- Sumo_config -> Content or config handled by the CMS. No work expected. | |||
*[https://bugzilla.mozilla.org/show_bug.cgi?id=500047 SUMO should not be loading images from personal hosting servers] | |||
*[https://bugzilla.mozilla.org/show_bug.cgi?id=401067 New contributors cannot edit staging copies] | |||
*[https://bugzilla.mozilla.org/show_bug.cgi?id=388844 I (Chris Ilias) need more privileges on sumo staging site] | |||
4- sumo_onetime -> One time issue with load, etc. that we don't expect to ever deal with again. No work expected. But of course, we may discover new weird things. | |||
*[https://bugzilla.mozilla.org/show_bug.cgi?id=470550 Database replication died in the C01 cluster due to overfilling sphinx tables] | |||
5- sumo_included -> Stuff which is included already in another meta-bug (ex.: showfor, screencast, CSAT, minify, adding locales, etc.), as listed on [[Support/TikiUpstreamTriage]]. Please note that this could be a sumo_feature (like in-product) or a tiki_feature that should be upstreamed (ex.: showfor). The idea is that we upstream or port to Tiki4 only the latest version, which combines all previous Bugzilla items. | |||
*[https://bugzilla.mozilla.org/show_bug.cgi?id=425834 SHOWFOR doesn't hide text with headings] | |||
*[https://bugzilla.mozilla.org/show_bug.cgi?id=474842 SHOWFOR browser detection is not working] | |||
*[https://bugzilla.mozilla.org/show_bug.cgi?id=497218 IE 6 / 7 / 8 Screencasts won't render in Internet Explorer (all versions)] | |||
*[https://bugzilla.mozilla.org/show_bug.cgi?id=497459 Make screencast preview not insert {SCREENCAST} snippet] | |||
*[https://bugzilla.mozilla.org/show_bug.cgi?id=482532 es-MX Enable Spanish (Mexico) localization on SUMO] | |||
*[https://bugzilla.mozilla.org/show_bug.cgi?id=485644 Remove es-MX locale (revert Bug 482532)] | |||
*[https://bugzilla.mozilla.org/show_bug.cgi?id=480463 Layout broken in Safari 3.2.1 / IE 6 due to Minify] | |||
6- sumo-nottiki -> This would be things which have nothing to do with Tiki. Thus zero impact if we upgrade or not. | |||
* MySQL errors, etc. | |||
7- sumo-tools -> Things like load tester. Here, perhaps we need to evaluate if it makes a difference if we upgrade or fork. | |||
So, most of the items of sumo_only should be not too much work. | |||
However, | |||
1- The meta bugs can be huge | |||
2- We'll have new features but also new bugs in Tiki4 (especially performance because no one stress-tested) | |||